WSL2-Linux-Kernel/samples
Ross Zwisler 27d7fdf06f 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>
2023-03-13 21:51:30 -07:00
..
acrn
auxdisplay
binderfs
bpf bpf: use canonical ftrace path 2023-03-13 21:51:30 -07:00
configfs
connector
coresight
fanotify
fprobe
ftrace
hid
hidraw
hw_breakpoint
kdb
kfifo
kmemleak
kobject
kprobes
landlock
livepatch
mei
nitro_enclaves
pidfd
pktgen
qmi
rpmsg
rust
seccomp
timers
trace_events
trace_printk
uhid
user_events
v4l
vfio-mdev VFIO updates for v6.3-rc1 2023-02-25 11:52:57 -08:00
vfs
watch_queue
watchdog
Kconfig VFIO updates for v6.3-rc1 2023-02-25 11:52:57 -08:00
Makefile