diff options
author | Ross Zwisler <zwisler@google.com> | 2023-03-13 23:56:27 +0300 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2023-03-14 07:51:30 +0300 |
commit | 27d7fdf06fdb84455ff585b58c8034e2fab42583 (patch) | |
tree | 6db438ddc306f32e69758cbcc1d69cbf3e10e298 /tools/testing/selftests/bpf/trace_helpers.c | |
parent | 9e36a204bd43553a9cd4bd574612cd9a5df791ea (diff) | |
download | linux-27d7fdf06fdb84455ff585b58c8034e2fab42583.tar.xz |
bpf: 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 samples in the bpf code still refer to this older
debugfs path, so let's update them to avoid confusion. There are a few
spots where the bpf code explicitly checks both tracefs and debugfs
(tools/bpf/bpftool/tracelog.c and tools/lib/api/fs/fs.c) and I've left
those alone so that the tools can continue to work with both paths.
Signed-off-by: Ross Zwisler <zwisler@google.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Link: https://lore.kernel.org/r/20230313205628.1058720-2-zwisler@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/testing/selftests/bpf/trace_helpers.c')
0 files changed, 0 insertions, 0 deletions