From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>,
Pekka Enberg <penberg@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 3/3] perf report: Add --show-time-info option
Date: Wed, 4 Dec 2013 09:57:03 -0300 [thread overview]
Message-ID: <20131204125703.GA6359@ghostprotocols.net> (raw)
In-Reply-To: <20131204101117.GC2363@gmail.com>
Em Wed, Dec 04, 2013 at 11:11:17AM +0100, Ingo Molnar escreveu:
> * Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> > Em Mon, Dec 02, 2013 at 12:58:35PM -0700, David Ahern escreveu:
> > > On 12/2/13, 12:38 PM, Arnaldo Carvalho de Melo wrote:
> > > Why not just --event-time?
> > > Really should have dropped the 'show' from the recent perf-script
> > > change (just --task-events and --mmap-events).
> > Probably, yeah, Ingo made some point about using --show- for some reason,
> > Ingo?
> So the reason for my suggestion was that I've noticed a proliferation
> of such flags in perf report. To reduce namespace pollution it's
> always good to bring a certain kind of hierarchy into command line
> options.
> Options that work alike should spell alike. Users shouldn't be
> required to memorize every naming quirk of the various disjunct
> 'display this extra data' options.
> So if we expect more --show options in the future (and in particular
> if there are existing oddball options that could be changed to the
> --show-xyz pattern) then I'd suggest to do it unified. For example
> there's --show-nr-samples and --show-info already which follows this
> pattern.
> This pattern would distinguish this option from the other perf report
> options, such as --vmlinux, --force, --sort, etc.
> It might even make sense to unify it all into a single --show option.
> That would allow the following current mismash of options:
> --task-events --mmap-events --show-nr-samples --show-info
> to be replaced by a much more obvious, much more coherent looking
> option sequence:
> --show task-events,mmap-events,nr-samples,info
Excellent idea, agreed, we should probably try to implement this as a
generic facility to be used accross all the tools.
This, together with the other options processing code should be a
natural candidate for a tools/lib/opt/ directory, implemented in the way
we discussed: a .a for tools that want all the options processing, but
also as untangled as possible so that tools that want just specific bits
can chew them individually.
So, in summary, we _will_ be dropping the 'show-' prefix from all those
options, and those options as well, that then just become a single (top
level) option with entries in a bitmask that are set via some OPT_
callback that receives some struct with a string table and has a bitmask
that it will set.
> an added bonus would be that '--show help' could be implemented as
> well, to list all displayable extra data.
Right, the string table I mentioned in fact should be a struct table
that in turn has two strings, the --show bitname and bithelp.
> (I'm not married to the specific naming, it could be something else as
> well, like --display or --report.)
I think 'show' is ok, 4 letters, shorter than 'display', already used in
several places.
- Arnaldo
next prev parent reply other threads:[~2013-12-04 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 19:23 [PATCH 3/3] perf report: Add --show-time-info option Arnaldo Carvalho de Melo
2013-12-02 19:25 ` David Ahern
2013-12-02 19:38 ` Arnaldo Carvalho de Melo
2013-12-02 19:58 ` David Ahern
2013-12-02 20:17 ` Arnaldo Carvalho de Melo
2013-12-02 20:22 ` David Ahern
2013-12-04 10:11 ` Ingo Molnar
2013-12-04 12:57 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-02 6:53 [RFC 0/3] perf tools: Show time info (v1) Namhyung Kim
2013-12-02 6:53 ` [PATCH 3/3] perf report: Add --show-time-info option Namhyung Kim
2013-12-02 12:33 ` Arnaldo Carvalho de Melo
2013-12-02 14:38 ` Namhyung Kim
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=20131204125703.GA6359@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=penberg@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