blob: c7f5f55634ac3fab974216404fdcb6348aec94d0 [file] [log] [blame]
Hitoshi Mitake84c6f882010-02-04 16:08:15 +09001perf-lock(1)
2============
3
4NAME
5----
6perf-lock - Analyze lock events
7
8SYNOPSIS
9--------
10[verse]
Namhyung Kimd1eec3e2012-01-29 17:55:56 +090011'perf lock' {record|report|script|info}
Hitoshi Mitake84c6f882010-02-04 16:08:15 +090012
13DESCRIPTION
14-----------
15You can analyze various lock behaviours
16and statistics with this 'perf lock' command.
17
18 'perf lock record <command>' records lock events
19 between start and end <command>. And this command
20 produces the file "perf.data" which contains tracing
21 results of lock events.
22
Hitoshi Mitake84c6f882010-02-04 16:08:15 +090023 'perf lock report' reports statistical data.
24
Namhyung Kimd1eec3e2012-01-29 17:55:56 +090025 'perf lock script' shows raw lock events.
26
27 'perf lock info' shows metadata like threads or addresses
28 of lock instances.
29
Marcin Slusarz9826e832011-02-22 21:53:12 +010030COMMON OPTIONS
31--------------
Shawn Bohrer4aace252010-11-30 19:57:14 -060032
33-i::
34--input=<file>::
Robert Richterefad1412011-12-07 10:02:54 +010035 Input file name. (default: perf.data unless stdin is a fifo)
Shawn Bohrer4aace252010-11-30 19:57:14 -060036
37-v::
38--verbose::
39 Be more verbose (show symbol address, etc).
40
41-D::
42--dump-raw-trace::
43 Dump raw trace in ASCII.
44
Marcin Slusarz9826e832011-02-22 21:53:12 +010045REPORT OPTIONS
46--------------
47
48-k::
49--key=<value>::
50 Sorting key. Possible values: acquired (default), contended,
51 wait_total, wait_max, wait_min.
52
Namhyung Kimd1eec3e2012-01-29 17:55:56 +090053INFO OPTIONS
54------------
55
56-t::
57--threads::
58 dump thread list in perf.data
59
60-m::
61--map::
62 dump map of lock instances (address:name table)
63
Hitoshi Mitake84c6f882010-02-04 16:08:15 +090064SEE ALSO
65--------
66linkperf:perf[1]