summaryrefslogtreecommitdiffstats
path: root/kernel/trace/kprobe_event_gen_test.c
diff options
context:
space:
mode:
authorRoss Zwisler <zwisler@chromium.org>2023-02-15 15:33:45 -0700
committerSteven Rostedt (Google) <rostedt@goodmis.org>2023-02-18 14:34:09 -0500
commit2455f0e124d317dd08d337a7550a78a224d4ba41 (patch)
treea26318d9852d06d95c8f68740fe5e3e7de3a4c1d /kernel/trace/kprobe_event_gen_test.c
parentd8f0ae3ebed416728077fe94698983c30d409241 (diff)
downloadlinux-2455f0e124d317dd08d337a7550a78a224d4ba41.tar.gz
linux-2455f0e124d317dd08d337a7550a78a224d4ba41.tar.bz2
linux-2455f0e124d317dd08d337a7550a78a224d4ba41.zip
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>
Diffstat (limited to 'kernel/trace/kprobe_event_gen_test.c')
-rw-r--r--kernel/trace/kprobe_event_gen_test.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/trace/kprobe_event_gen_test.c b/kernel/trace/kprobe_event_gen_test.c
index c736487fc0e4..4850fdfe27f1 100644
--- a/kernel/trace/kprobe_event_gen_test.c
+++ b/kernel/trace/kprobe_event_gen_test.c
@@ -21,7 +21,7 @@
* Then:
*
* # insmod kernel/trace/kprobe_event_gen_test.ko
- * # cat /sys/kernel/debug/tracing/trace
+ * # cat /sys/kernel/tracing/trace
*
* You should see many instances of the "gen_kprobe_test" and
* "gen_kretprobe_test" events in the trace buffer.