From: Andi Kleen <andi@firstfloor.org>
To: acme@ghostprotocols.net
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com,
eranian@google.com, Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 3/3] perf: Clarify -c help text
Date: Thu, 15 Sep 2011 14:31:42 -0700 [thread overview]
Message-ID: <1316122302-24306-3-git-send-email-andi@firstfloor.org> (raw)
In-Reply-To: <1316122302-24306-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
Clarify what perf record/top -c actually does in the help text.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
tools/perf/Documentation/perf-record.txt | 6 +++---
tools/perf/Documentation/perf-top.txt | 2 +-
tools/perf/builtin-record.c | 2 +-
tools/perf/builtin-top.c | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
index 5a520f8..f636cc8 100644
--- a/tools/perf/Documentation/perf-record.txt
+++ b/tools/perf/Documentation/perf-record.txt
@@ -72,9 +72,9 @@ OPTIONS
--force::
Overwrite existing data file. (deprecated)
--c::
---count=::
- Event period to sample.
+-cN::
+--count=N::
+ Sample event every N occurrences.
-o::
--output=::
diff --git a/tools/perf/Documentation/perf-top.txt b/tools/perf/Documentation/perf-top.txt
index f6eb1cd..b6043b0 100644
--- a/tools/perf/Documentation/perf-top.txt
+++ b/tools/perf/Documentation/perf-top.txt
@@ -23,7 +23,7 @@ OPTIONS
-c <count>::
--count=<count>::
- Event period to sample.
+ Sample event every COUNT occurrences.
-C <cpu-list>::
--cpu=<cpu>::
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
index 042117f..22a9a27 100644
--- a/tools/perf/builtin-record.c
+++ b/tools/perf/builtin-record.c
@@ -761,7 +761,7 @@ const struct option record_options[] = {
"list of cpus to monitor"),
OPT_BOOLEAN('f', "force", &force,
"overwrite existing data file (deprecated)"),
- OPT_U64('c', "count", &user_interval, "event period to sample"),
+ OPT_U64('c', "count", &user_interval, "sample every COUNTS events"),
OPT_STRING('o', "output", &output_name, "file",
"output file name"),
OPT_BOOLEAN('i', "no-inherit", &no_inherit,
diff --git a/tools/perf/builtin-top.c b/tools/perf/builtin-top.c
index a43433f..79bfb5d 100644
--- a/tools/perf/builtin-top.c
+++ b/tools/perf/builtin-top.c
@@ -992,7 +992,7 @@ static const struct option options[] = {
"event selector. use 'perf list' to list available events",
parse_events_option),
OPT_INTEGER('c', "count", &default_interval,
- "event period to sample"),
+ "sample event every N occurrences"),
OPT_INTEGER('p', "pid", &top.target_pid,
"profile events on existing process id"),
OPT_INTEGER('t', "tid", &top.target_tid,
--
1.7.4.4
prev parent reply other threads:[~2011-09-15 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 21:31 [PATCH 1/3] perf: Make perf stat/record print fatal signals of the target program Andi Kleen
2011-09-15 21:31 ` [PATCH 2/3] perf: Support setting the disassembler style Andi Kleen
2011-09-16 14:27 ` Arnaldo Carvalho de Melo
2011-09-15 21:31 ` Andi Kleen [this message]
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=1316122302-24306-3-git-send-email-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.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