c1cda36fc5
Bugzilla: https://bugzilla.redhat.com/2233483 upstream ======== commit 2455f0e124d317dd08d337a7550a78a224d4ba41 Author: Ross Zwisler <zwisler@chromium.org> Date: Wed Feb 15 15:33:45 2023 -0700 description =========== 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> Conflicts: ========== We don't have samples/user_events/example.c . Signed-off-by: Michael Petlan <mpetlan@redhat.com> |
||
|---|---|---|
| .. | ||
| draw_functrace.py | ||
| ftrace-bisect.sh | ||