Minki/linux
1
0
Fork 1
mirror of https://github.com/torvalds/linux.git synced 2024-09-20 15:03:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

perf tools docs: Use canonical ftrace path

Browse Source 
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

A few spots in the perf docs still refer to this older debugfs path, so
let's update them to avoid confusion.

Signed-off-by: Ross Zwisler <zwisler@google.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
Cc: linux-trace-kernel@vger.kernel.org
Link: http://lore.kernel.org/lkml/20230130181915.1113313-5-zwisler@google.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
This commit is contained in:
Ross Zwisler 2023-01-30 11:19:10 -07:00 committed by Arnaldo Carvalho de Melo
parent 2889959489
commit 1df49ef9ee
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tools/perf/Documentation/perf-list.txt
View File

@ -232,7 +232,7 @@ This can be overridden by setting the kernel.perf_event_paranoid
sysctl to -1, which allows non root to use these events. sysctl to -1, which allows non root to use these events.
For accessing trace point events perf needs to have read access to For accessing trace point events perf needs to have read access to
/sys/kernel/debug/tracing, even when perf_event_paranoid is in a relaxed /sys/kernel/tracing, even when perf_event_paranoid is in a relaxed
setting. setting.
TRACING TRACING

2
tools/perf/Documentation/perf-script-perl.txt
View File

@ -55,7 +55,7 @@ Traces meant to be processed using a script should be recorded with
the above option: -a to enable system-wide collection. the above option: -a to enable system-wide collection.
The format file for the sched_wakeup event defines the following fields The format file for the sched_wakeup event defines the following fields
(see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format): (see /sys/kernel/tracing/events/sched/sched_wakeup/format):
---- ----
format: format:

4
tools/perf/Documentation/perf-script-python.txt
View File

@ -319,7 +319,7 @@ So those are the essential steps in writing and running a script. The
process can be generalized to any tracepoint or set of tracepoints process can be generalized to any tracepoint or set of tracepoints
you're interested in - basically find the tracepoint(s) you're you're interested in - basically find the tracepoint(s) you're
interested in by looking at the list of available events shown by interested in by looking at the list of available events shown by
'perf list' and/or look in /sys/kernel/debug/tracing/events/ for 'perf list' and/or look in /sys/kernel/tracing/events/ for
detailed event and field info, record the corresponding trace data detailed event and field info, record the corresponding trace data
using 'perf record', passing it the list of interesting events, using 'perf record', passing it the list of interesting events,
generate a skeleton script using 'perf script -g python' and modify the generate a skeleton script using 'perf script -g python' and modify the
@ -449,7 +449,7 @@ Traces meant to be processed using a script should be recorded with
the above option: -a to enable system-wide collection. the above option: -a to enable system-wide collection.
The format file for the sched_wakeup event defines the following fields The format file for the sched_wakeup event defines the following fields
(see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format): (see /sys/kernel/tracing/events/sched/sched_wakeup/format):
---- ----
format: format: