1PERF-TRACE(1) perf Manual PERF-TRACE(1)
2
3
4
6 perf-trace - Read perf.data (created by perf record) and display trace
7 output
8
10 perf trace {record <script> | report <script> [args] }
11
13 This command reads the input file and displays the trace recorded.
14
15 There are several variants of perf trace:
16
17 'perf trace' to see a detailed trace of the workload that was
18 recorded.
19
20 You can also run a set of pre-canned scripts that aggregate and
21 summarize the raw trace data in various ways (the list of scripts is
22 available via 'perf trace -l'). The following variants allow you to
23 record and run those scripts:
24
25 'perf trace record <script>' to record the events required for 'perf
26 trace report'. <script> is the name displayed in the output of
27 'perf trace --list' i.e. the actual script name minus any language
28 extension.
29
30 'perf trace report <script>' to run and display the results of
31 <script>. <script> is the name displayed in the output of 'perf
32 trace --list' i.e. the actual script name minus any language
33 extension. The perf.data output from a previous run of 'perf trace
34 record <script>' is used and should be present for this command to
35 succeed.
36
37 See the 'SEE ALSO' section for links to language-specific
38 information on how to write and run your own trace scripts.
39
41 -D, --dump-raw-trace=
42 Display verbose dump of the trace data.
43
44 -L, --Latency=
45 Show latency attributes (irqs/preemption disabled, etc).
46
47 -l, --list=
48 Display a list of available trace scripts.
49
50 -s [lang], --script=
51 Process trace data with the given script ([lang]:script[.ext]). If
52 the string lang is specified in place of a script name, a list of
53 supported languages will be displayed instead.
54
55 -g, --gen-script=
56 Generate perf-trace.[ext] starter script for given language, using
57 current perf.data.
58
60 perf-record(1), perf-trace-perl(1), perf-trace-python(1)
61
62
63
64perf 2.6.35.14-106.fc 11/23/2011 PERF-TRACE(1)