forked from luck/tmp_suning_uos_patched
perf trace/scripting: Update Documentation
Update the perf-trace page with new and missing options and remove some unused ones. Signed-off-by: Tom Zanussi <tzanussi@gmail.com> Cc: fweisbec@gmail.com Cc: rostedt@goodmis.org LKML-Reference: <1260867220-15699-7-git-send-email-tzanussi@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
parent
3875294f5c
commit
a6005123ce
@ -8,18 +8,43 @@ perf-trace - Read perf.data (created by perf record) and display trace output
|
||||
SYNOPSIS
|
||||
--------
|
||||
[verse]
|
||||
'perf trace' [-i <file> | --input=file] symbol_name
|
||||
'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.
|
||||
|
||||
'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.
|
||||
|
||||
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::
|
||||
--script=::
|
||||
Process trace data with the given script ([lang]:script[.ext]).
|
||||
|
Loading…
Reference in New Issue
Block a user