mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-22 12:14:01 +08:00
84c6f88fc8
I've forgot to add 'perf lock' line to command-list.txt, so users of perf could not find perf lock when they type 'perf'. Fixing command-list.txt requires document (tools/perf/Documentation/perf-lock.txt). But perf lock is too much "under construction" to write a stable document, so this is something like pseudo document for now. And I wrote description of perf lock at help section of CONFIG_LOCK_STAT, this will navigate users of lock trace events. Signed-off-by: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Paul Mackerras <paulus@samba.org> Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net> LKML-Reference: <1265267295-8388-1-git-send-email-mitake@dcl.info.waseda.ac.jp> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
30 lines
554 B
Plaintext
30 lines
554 B
Plaintext
perf-lock(1)
|
|
============
|
|
|
|
NAME
|
|
----
|
|
perf-lock - Analyze lock events
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf lock' {record|report|trace}
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
You can analyze various lock behaviours
|
|
and statistics with this 'perf lock' command.
|
|
|
|
'perf lock record <command>' records lock events
|
|
between start and end <command>. And this command
|
|
produces the file "perf.data" which contains tracing
|
|
results of lock events.
|
|
|
|
'perf lock trace' shows raw lock events.
|
|
|
|
'perf lock report' reports statistical data.
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf[1]
|