blob: 4a26a2f3a6a39a2da7e3954fdc8fed59c6647f20 [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]
11'perf lock' {record|report|trace}
12
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
23 'perf lock trace' shows raw lock events.
24
25 'perf lock report' reports statistical data.
26
Marcin Slusarz9826e832011-02-22 21:53:12 +010027COMMON OPTIONS
28--------------
Shawn Bohrer4aace252010-11-30 19:57:14 -060029
30-i::
31--input=<file>::
32 Input file name.
33
34-v::
35--verbose::
36 Be more verbose (show symbol address, etc).
37
38-D::
39--dump-raw-trace::
40 Dump raw trace in ASCII.
41
Marcin Slusarz9826e832011-02-22 21:53:12 +010042REPORT OPTIONS
43--------------
44
45-k::
46--key=<value>::
47 Sorting key. Possible values: acquired (default), contended,
48 wait_total, wait_max, wait_min.
49
Hitoshi Mitake84c6f882010-02-04 16:08:15 +090050SEE ALSO
51--------
52linkperf:perf[1]