From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] perf, record: Ammend option summaries
Date: Wed, 10 Jun 2015 14:27:43 -0300 [thread overview]
Message-ID: <20150610172743.GN3136@kernel.org> (raw)
In-Reply-To: <20150610144850.GP19282@twins.programming.kicks-ass.net>
Em Wed, Jun 10, 2015 at 04:48:50PM +0200, Peter Zijlstra escreveu:
>
> Because there's too many options and I cannot read, I frequently get
> confused between -c and -P, and try to do things like:
>
> perf record -P 50000 -- foo
>
> Which does not work; try and make the option description slightly longer
> and hopefully less confusing.
Thanks, I'll check and update tools/perf/Documentation/perf-record.txt,
i.e. the man page.
- Arnaldo
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> tools/perf/builtin-record.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index d3731cc..4d6cdeb 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -1027,10 +1027,9 @@ struct option __record_options[] = {
> OPT_BOOLEAN('q', "quiet", &quiet, "don't print any message"),
> OPT_BOOLEAN('s', "stat", &record.opts.inherit_stat,
> "per thread counts"),
> - OPT_BOOLEAN('d', "data", &record.opts.sample_address,
> - "Sample addresses"),
> - OPT_BOOLEAN('T', "timestamp", &record.opts.sample_time, "Sample timestamps"),
> - OPT_BOOLEAN('P', "period", &record.opts.period, "Sample period"),
> + OPT_BOOLEAN('d', "data", &record.opts.sample_address, "Record the sample addresses"),
> + OPT_BOOLEAN('T', "timestamp", &record.opts.sample_time, "Record the sample timestamps"),
> + OPT_BOOLEAN('P', "period", &record.opts.period, "Record the sample period"),
> OPT_BOOLEAN('n', "no-samples", &record.opts.no_samples,
> "don't sample"),
> OPT_BOOLEAN('N', "no-buildid-cache", &record.no_buildid_cache,
next prev parent reply other threads:[~2015-06-10 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 14:48 [PATCH] perf, record: Ammend option summaries Peter Zijlstra
2015-06-10 17:27 ` Arnaldo Carvalho de Melo [this message]
2015-06-11 8:46 ` Peter Zijlstra
2015-06-11 13:58 ` Arnaldo Carvalho de Melo
2015-06-12 8:49 ` [tip:perf/core] perf record: Amend " tip-bot for Peter Zijlstra
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=20150610172743.GN3136@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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