1perf-lock(1)
2============
3
4NAME
5----
6perf-lock - Analyze lock events
7
8SYNOPSIS
9--------
10[verse]
11'perf lock' {record|report|script|info}
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 report' reports statistical data.
24
25  'perf lock script' shows raw lock events.
26
27  'perf lock info' shows metadata like threads or addresses
28  of lock instances.
29
30COMMON OPTIONS
31--------------
32
33-i::
34--input=<file>::
35        Input file name. (default: perf.data unless stdin is a fifo)
36
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
45-f::
46--force::
47	Don't complain, do it.
48
49REPORT OPTIONS
50--------------
51
52-k::
53--key=<value>::
54        Sorting key. Possible values: acquired (default), contended,
55	avg_wait, wait_total, wait_max, wait_min.
56
57-F::
58--field=<value>::
59        Output fields. By default it shows all the fields but users can
60	customize that using this.  Possible values: acquired, contended,
61	avg_wait, wait_total, wait_max, wait_min.
62
63-c::
64--combine-locks::
65	Merge lock instances in the same class (based on name).
66
67INFO OPTIONS
68------------
69
70-t::
71--threads::
72	dump thread list in perf.data
73
74-m::
75--map::
76	dump map of lock instances (address:name table)
77
78SEE ALSO
79--------
80linkperf:perf[1]
81