6 perf-trace - Read perf.data (created by perf record) and display trace output
11 'perf trace' {record <script> | report <script> [args] }
15 This command reads the input file and displays the trace recorded.
17 There are several variants of perf trace:
19 'perf trace' to see a detailed trace of the workload that was
22 You can also run a set of pre-canned scripts that aggregate and
23 summarize the raw trace data in various ways (the list of scripts is
24 available via 'perf trace -l'). The following variants allow you to
25 record and run those scripts:
27 'perf trace record <script>' to record the events required for 'perf
28 trace report'. <script> is the name displayed in the output of
29 'perf trace --list' i.e. the actual script name minus any language
32 'perf trace report <script>' to run and display the results of
33 <script>. <script> is the name displayed in the output of 'perf
34 trace --list' i.e. the actual script name minus any language
35 extension. The perf.data output from a previous run of 'perf trace
36 record <script>' is used and should be present for this command to
39 See the 'SEE ALSO' section for links to language-specific
40 information on how to write and run your own trace scripts.
46 Display verbose dump of the trace data.
50 Show latency attributes (irqs/preemption disabled, etc).
54 Display a list of available trace scripts.
58 Process trace data with the given script ([lang]:script[.ext]).
59 If the string 'lang' is specified in place of a script name, a
60 list of supported languages will be displayed instead.
64 Generate perf-trace.[ext] starter script for given language,
65 using current perf.data.
69 linkperf:perf-record[1], linkperf:perf-trace-perl[1],
70 linkperf:perf-trace-python[1]