perf script: Add support for dumping symbols
[linux-2.6-block.git] / tools / perf / Documentation / perf-script.txt
CommitLineData
133dc4c3 1perf-script(1)
4778e0e8 2=============
0a02ad93
IM
3
4NAME
5----
133dc4c3 6perf-script - Read perf.data (created by perf record) and display trace output
0a02ad93
IM
7
8SYNOPSIS
9--------
10[verse]
133dc4c3
IM
11'perf script' [<options>]
12'perf script' [<options>] record <script> [<record-options>] <command>
13'perf script' [<options>] report <script> [script-args]
14'perf script' [<options>] <script> <required-script-args> [<record-options>] <command>
15'perf script' [<options>] <top-script> [script-args]
0a02ad93
IM
16
17DESCRIPTION
18-----------
19This command reads the input file and displays the trace recorded.
20
133dc4c3 21There are several variants of perf script:
a6005123 22
133dc4c3 23 'perf script' to see a detailed trace of the workload that was
a6005123
TZ
24 recorded.
25
cff68e58
TZ
26 You can also run a set of pre-canned scripts that aggregate and
27 summarize the raw trace data in various ways (the list of scripts is
133dc4c3 28 available via 'perf script -l'). The following variants allow you to
cff68e58
TZ
29 record and run those scripts:
30
133dc4c3
IM
31 'perf script record <script> <command>' to record the events required
32 for 'perf script report'. <script> is the name displayed in the
33 output of 'perf script --list' i.e. the actual script name minus any
d3c4f798
TZ
34 language extension. If <command> is not specified, the events are
35 recorded using the -a (system-wide) 'perf record' option.
a6005123 36
133dc4c3 37 'perf script report <script> [args]' to run and display the results
d3c4f798 38 of <script>. <script> is the name displayed in the output of 'perf
a6005123 39 trace --list' i.e. the actual script name minus any language
133dc4c3 40 extension. The perf.data output from a previous run of 'perf script
a6005123 41 record <script>' is used and should be present for this command to
d3c4f798
TZ
42 succeed. [args] refers to the (mainly optional) args expected by
43 the script.
44
133dc4c3 45 'perf script <script> <required-script-args> <command>' to both
d3c4f798
TZ
46 record the events required for <script> and to run the <script>
47 using 'live-mode' i.e. without writing anything to disk. <script>
133dc4c3 48 is the name displayed in the output of 'perf script --list' i.e. the
d3c4f798
TZ
49 actual script name minus any language extension. If <command> is
50 not specified, the events are recorded using the -a (system-wide)
51 'perf record' option. If <script> has any required args, they
52 should be specified before <command>. This mode doesn't allow for
53 optional script args to be specified; if optional script args are
133dc4c3
IM
54 desired, they can be specified using separate 'perf script record'
55 and 'perf script report' commands, with the stdout of the record step
d3c4f798
TZ
56 piped to the stdin of the report script, using the '-o -' and '-i -'
57 options of the corresponding commands.
58
133dc4c3 59 'perf script <top-script>' to both record the events required for
d3c4f798
TZ
60 <top-script> and to run the <top-script> using 'live-mode'
61 i.e. without writing anything to disk. <top-script> is the name
133dc4c3 62 displayed in the output of 'perf script --list' i.e. the actual
d3c4f798
TZ
63 script name minus any language extension; a <top-script> is defined
64 as any script name ending with the string 'top'.
65
133dc4c3 66 [<record-options>] can be passed to the record steps of 'perf script
d3c4f798 67 record' and 'live-mode' variants; this isn't possible however for
133dc4c3 68 <top-script> 'live-mode' or 'perf script report' variants.
a6005123 69
cff68e58
TZ
70 See the 'SEE ALSO' section for links to language-specific
71 information on how to write and run your own trace scripts.
72
0a02ad93
IM
73OPTIONS
74-------
d3c4f798
TZ
75<command>...::
76 Any command you can specify in a shell.
77
0a02ad93 78-D::
133dc4c3 79--dump-raw-script=::
0a02ad93
IM
80 Display verbose dump of the trace data.
81
a6005123
TZ
82-L::
83--Latency=::
84 Show latency attributes (irqs/preemption disabled, etc).
85
86-l::
87--list=::
88 Display a list of available trace scripts.
89
f526d68b 90-s ['lang']::
89fbf0b8
TZ
91--script=::
92 Process trace data with the given script ([lang]:script[.ext]).
f526d68b
TZ
93 If the string 'lang' is specified in place of a script name, a
94 list of supported languages will be displayed instead.
89fbf0b8
TZ
95
96-g::
97--gen-script=::
133dc4c3 98 Generate perf-script.[ext] starter script for given language,
89fbf0b8
TZ
99 using current perf.data.
100
d3c4f798
TZ
101-a::
102 Force system-wide collection. Scripts run without a <command>
103 normally use -a by default, while scripts run with a <command>
104 normally don't - this option allows the latter to be run in
105 system-wide mode.
106
646420f1
SB
107-i::
108--input=::
109 Input file name.
110
111-d::
112--debug-mode::
113 Do various checks like samples ordering and lost events.
d3c4f798 114
745f43e3
DA
115-f::
116--fields
117 Comma separated list of fields to print. Options are:
c0230b2b
DA
118 comm, tid, pid, time, cpu, event, trace, sym
119
120-k::
121--vmlinux=<file>::
122 vmlinux pathname
123
124--kallsyms=<file>::
125 kallsyms pathname
126
127--symfs=<directory>::
128 Look for files with symbols relative to this directory.
129
130-G::
131--hide-call-graph::
132 When printing symbols do not display call chain.
745f43e3 133
0a02ad93
IM
134SEE ALSO
135--------
133dc4c3
IM
136linkperf:perf-record[1], linkperf:perf-script-perl[1],
137linkperf:perf-script-python[1]