lkml.org 
[lkml]   [2017]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[tip:perf/urgent] perf script: Fix documentation errors
    Commit-ID:  34d4453dac257be53c21abf2f713c992fb692b5c
    Gitweb: http://git.kernel.org/tip/34d4453dac257be53c21abf2f713c992fb692b5c
    Author: SeongJae Park <sj38.park@gmail.com>
    AuthorDate: Tue, 30 May 2017 20:18:24 +0900
    Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
    CommitDate: Wed, 7 Jun 2017 20:27:20 -0300

    perf script: Fix documentation errors

    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: cff68e582237 ("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>
    ---
    tools/perf/Documentation/perf-script-perl.txt | 2 +-
    tools/perf/Documentation/perf-script-python.txt | 4 ++--
    2 files changed, 3 insertions(+), 3 deletions(-)

    diff --git a/tools/perf/Documentation/perf-script-perl.txt b/tools/perf/Documentation/perf-script-perl.txt
    index dfbb506..142606c 100644
    --- a/tools/perf/Documentation/perf-script-perl.txt
    +++ b/tools/perf/Documentation/perf-script-perl.txt
    @@ -39,7 +39,7 @@ EVENT HANDLERS
    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
    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.

    Most of the event's field values are passed as arguments to the
    diff --git a/tools/perf/Documentation/perf-script-python.txt b/tools/perf/Documentation/perf-script-python.txt
    index 54acba2..087b87c9 100644
    --- a/tools/perf/Documentation/perf-script-python.txt
    +++ b/tools/perf/Documentation/perf-script-python.txt
    @@ -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
    you're interested in - basically find the tracepoint(s) you're
    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
    using 'perf record', passing it the list of interesting events,
    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
    '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
    -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.

    Most of the event's field values are passed as arguments to the
    \
     
     \ /
      Last update: 2017-06-12 01:37    [W:4.613 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site