GitHub-Mirror/Star64_linux
2
0
Fork 0
mirror of https://github.com/Fishwaldo/Star64_linux.git synced 2025-06-23 07:01:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

perf script: Fix documentation errors

Browse source 
This commit fixes two errors in documents for perf-script-python and
perf-script-perl as below:

- /sys/kernel/debug/tracing events -> /sys/kernel/debug/tracing/events/
- trace_handled -> trace_unhandled

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Tom Zanussi <tzanussi@gmail.com>
Fixes: cff68e5822 ("perf/scripts: Add perf-trace-python Documentation")
Link: http://lkml.kernel.org/r/20170530111827.21732-3-sj38.park@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
This commit is contained in:
SeongJae Park 2017-05-30 20:18:24 +09:00 • committed by Arnaldo Carvalho de Melo
parent c76132dc51
commit 34d4453dac
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -39,7 +39,7 @@ EVENT HANDLERS
When perf script is invoked using a trace script, a user-defined When perf script is invoked using a trace script, a user-defined
'handler function' is called for each event in the trace. If there's 'handler function' is called for each event in the trace. If there's
no handler function defined for a given event type, the event is no handler function defined for a given event type, the event is
ignored (or passed to a 'trace_handled' function, see below) and the ignored (or passed to a 'trace_unhandled' function, see below) and the
next event is processed. next event is processed.
Most of the event's field values are passed as arguments to the Most of the event's field values are passed as arguments to the

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

@ -321,7 +321,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/debug/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
@ -437,7 +437,7 @@ EVENT HANDLERS
When perf script is invoked using a trace script, a user-defined When perf script is invoked using a trace script, a user-defined
'handler function' is called for each event in the trace. If there's 'handler function' is called for each event in the trace. If there's
no handler function defined for a given event type, the event is no handler function defined for a given event type, the event is
ignored (or passed to a 'trace_handled' function, see below) and the ignored (or passed to a 'trace_unhandled' function, see below) and the
next event is processed. next event is processed.
Most of the event's field values are passed as arguments to the Most of the event's field values are passed as arguments to the