mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-22 04:03:58 +08:00
cff68e5822
Also small update to perf-trace-perl and perf-trace docs. Signed-off-by: Tom 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: Frederic Weisbecker <fweisbec@gmail.com>
71 lines
2.0 KiB
Plaintext
71 lines
2.0 KiB
Plaintext
perf-trace(1)
|
|
==============
|
|
|
|
NAME
|
|
----
|
|
perf-trace - Read perf.data (created by perf record) and display trace output
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf trace' {record <script> | report <script> [args] }
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
This command reads the input file and displays the trace recorded.
|
|
|
|
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
|
|
extension.
|
|
|
|
'perf trace report <script>' to run and display the results of
|
|
<script>. <script> is the name displayed in the output of 'perf
|
|
trace --list' i.e. the actual script name minus any language
|
|
extension. The perf.data output from a previous run 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::
|
|
--dump-raw-trace=::
|
|
Display verbose dump of the trace data.
|
|
|
|
-L::
|
|
--Latency=::
|
|
Show latency attributes (irqs/preemption disabled, etc).
|
|
|
|
-l::
|
|
--list=::
|
|
Display a list of available trace scripts.
|
|
|
|
-s ['lang']::
|
|
--script=::
|
|
Process trace data with the given script ([lang]:script[.ext]).
|
|
If the string 'lang' is specified in place of a script name, a
|
|
list of supported languages will be displayed instead.
|
|
|
|
-g::
|
|
--gen-script=::
|
|
Generate perf-trace.[ext] starter script for given language,
|
|
using current perf.data.
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1], linkperf:perf-trace-perl[1],
|
|
linkperf:perf-trace-python[1]
|