-
- Downloads
tracing: Always use canonical ftrace path
The canonical location for the tracefs filesystem is at /sys/kernel/tracing. But, from Documentation/trace/ftrace.rst: Before 4.1, all ftrace tracing control files were within the debugfs file system, which is typically located at /sys/kernel/debug/tracing. For backward compatibility, when mounting the debugfs file system, the tracefs file system will be automatically mounted at: /sys/kernel/debug/tracing Many comments and Kconfig help messages in the tracing code still refer to this older debugfs path, so let's update them to avoid confusion. Link: https://lore.kernel.org/linux-trace-kernel/20230215223350.2658616-2-zwisler@google.com Acked-by:Masami Hiramatsu (Google) <mhiramat@kernel.org> Reviewed-by:
Mukesh Ojha <quic_mojha@quicinc.com> Signed-off-by:
Ross Zwisler <zwisler@google.com> Signed-off-by:
Steven Rostedt (Google) <rostedt@goodmis.org>
Showing
- include/linux/kernel.h 1 addition, 1 deletioninclude/linux/kernel.h
- include/linux/tracepoint.h 2 additions, 2 deletionsinclude/linux/tracepoint.h
- kernel/trace/Kconfig 10 additions, 10 deletionskernel/trace/Kconfig
- kernel/trace/kprobe_event_gen_test.c 1 addition, 1 deletionkernel/trace/kprobe_event_gen_test.c
- kernel/trace/ring_buffer.c 1 addition, 1 deletionkernel/trace/ring_buffer.c
- kernel/trace/synth_event_gen_test.c 1 addition, 1 deletionkernel/trace/synth_event_gen_test.c
- kernel/trace/trace.c 1 addition, 1 deletionkernel/trace/trace.c
- samples/user_events/example.c 2 additions, 2 deletionssamples/user_events/example.c
- scripts/tracing/draw_functrace.py 3 additions, 3 deletionsscripts/tracing/draw_functrace.py
- tools/lib/api/fs/tracing_path.c 2 additions, 2 deletionstools/lib/api/fs/tracing_path.c
- tools/tracing/latency/latency-collector.c 1 addition, 1 deletiontools/tracing/latency/latency-collector.c
Loading
Please register or sign in to comment