From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: linux-kernel@vger.kernel.org, Shawn Bohrer <shawn.bohrer@gmail.com>
Subject: [PATCH 06/14] perf: Document missing lock options
Date: Tue, 30 Nov 2010 19:57:14 -0600 [thread overview]
Message-ID: <1291168642-11402-7-git-send-email-shawn.bohrer@gmail.com> (raw)
In-Reply-To: <1291168642-11402-1-git-send-email-shawn.bohrer@gmail.com>
Signed-off-by: Shawn Bohrer <shawn.bohrer@gmail.com>
---
tools/perf/Documentation/perf-lock.txt | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/tools/perf/Documentation/perf-lock.txt b/tools/perf/Documentation/perf-lock.txt
index b317102..921de25 100644
--- a/tools/perf/Documentation/perf-lock.txt
+++ b/tools/perf/Documentation/perf-lock.txt
@@ -24,6 +24,21 @@ and statistics with this 'perf lock' command.
'perf lock report' reports statistical data.
+OPTIONS
+-------
+
+-i::
+--input=<file>::
+ Input file name.
+
+-v::
+--verbose::
+ Be more verbose (show symbol address, etc).
+
+-D::
+--dump-raw-trace::
+ Dump raw trace in ASCII.
+
SEE ALSO
--------
linkperf:perf[1]
--
1.7.3.2
next prev parent reply other threads:[~2010-12-01 2:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 1:57 [PATCH 00/14] perf documentation updates Shawn Bohrer
2010-12-01 1:57 ` [PATCH 01/14] perf: Document missing annotate options Shawn Bohrer
2010-12-02 11:42 ` [tip:perf/core] perf annotate: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 02/14] perf: Document missing buildid-list options Shawn Bohrer
2010-12-02 11:43 ` [tip:perf/core] perf buildid-list: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 03/14] perf: fix diff displacement and modules options short flag Shawn Bohrer
2010-12-02 11:43 ` [tip:perf/core] perf diff: Fix " tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 04/14] perf: Document missing diff options Shawn Bohrer
2010-12-02 11:43 ` [tip:perf/core] perf diff: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 05/14] perf: Document missing kvm options Shawn Bohrer
2010-12-02 11:44 ` [tip:perf/core] perf kvm: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` Shawn Bohrer [this message]
2010-12-02 11:44 ` [tip:perf/core] perf lock: " tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 07/14] perf: Fix spelling mistake in probe documentation Shawn Bohrer
2010-12-01 8:22 ` Masami Hiramatsu
2010-12-02 11:44 ` [tip:perf/core] perf probe: Fix spelling mistake in documentation tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 08/14] perf: Document missing record options Shawn Bohrer
2010-12-02 11:45 ` [tip:perf/core] perf record: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 09/14] perf: Document missing report options Shawn Bohrer
2010-12-02 11:45 ` [tip:perf/core] perf report: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 10/14] perf: Document missing sched options Shawn Bohrer
2010-12-02 11:46 ` [tip:perf/core] perf sched: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 11/14] perf: Document missing stat options Shawn Bohrer
2010-12-02 11:47 ` [tip:perf/core] perf stat: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 12/14] perf: Fix spelling mistake in test documentation Shawn Bohrer
2010-12-02 11:47 ` [tip:perf/core] perf test: Fix spelling mistake in documentation tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 13/14] perf: Document missing top options Shawn Bohrer
2010-12-02 11:46 ` [tip:perf/core] perf top: Document missing options tip-bot for Shawn Bohrer
2010-12-01 1:57 ` [PATCH 14/14] perf: Document missing trace options Shawn Bohrer
2010-12-02 11:46 ` [tip:perf/core] perf trace: Document missing options tip-bot for Shawn Bohrer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291168642-11402-7-git-send-email-shawn.bohrer@gmail.com \
--to=shawn.bohrer@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®