Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit cff68e58 authored by Tom Zanussi's avatar Tom Zanussi Committed by Frederic Weisbecker
Browse files

perf/scripts: Add perf-trace-python Documentation 



Also small update to perf-trace-perl and perf-trace docs.

Signed-off-by: default avatarTom Zanussi <tzanussi@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Keiichi KII <k-keiichi@bx.jp.nec.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <1264580883-15324-13-git-send-email-tzanussi@gmail.com>
Signed-off-by: default avatarFrederic Weisbecker <fweisbec@gmail.com>
parent 44ad9cd8

tools/perf/Documentation/perf-trace-perl.txt

+2 −1
Original line number Diff line number Diff line
@@ -8,7 +8,7 @@ perf-trace-perl - Process trace data with a Perl script 
SYNOPSIS

--------

[verse]

'perf trace' [-s [lang]:script[.ext] ]

'perf trace' [-s [Perl]:script[.pl] ]



DESCRIPTION

-----------
@@ -213,6 +213,7 @@ Various utility functions for use with perf trace: 
  nsecs_nsecs($nsecs) - returns nsecs remainder given nsecs

  nsecs_str($nsecs) - returns printable string in the form secs.nsecs

  avg($total, $n) - returns average given a sum and a total number of values

  syscall_name($id) - returns the syscall name for the specified syscall_nr



SEE ALSO

--------

tools/perf/Documentation/perf-trace-python.txt

0 → 100644
+624 −0

File added.

Preview size limit exceeded, changes collapsed.

tools/perf/Documentation/perf-trace.txt

+10 −1
Original line number Diff line number Diff line
@@ -19,6 +19,11 @@ There are several variants of perf trace: 
  'perf trace' to see a detailed trace of the workload that was

  recorded.



  You can also run a set of pre-canned scripts that aggregate and

  summarize the raw trace data in various ways (the list of scripts is

  available via 'perf trace -l').  The following variants allow you to

  record and run those scripts:



  'perf trace record <script>' to record the events required for 'perf

  trace report'.  <script> is the name displayed in the output of

  'perf trace --list' i.e. the actual script name minus any language
@@ -31,6 +36,9 @@ There are several variants of perf trace: 
  record <script>' is used and should be present for this command to

  succeed.



  See the 'SEE ALSO' section for links to language-specific

  information on how to write and run your own trace scripts.



OPTIONS

-------

-D::
@@ -58,4 +66,5 @@ OPTIONS 


SEE ALSO

--------

linkperf:perf-record[1], linkperf:perf-trace-perl[1]
 
linkperf:perf-record[1], linkperf:perf-trace-perl[1],

linkperf:perf-trace-python[1]