From: Namhyung Kim <namhyung@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: jolsa@redhat.com, linux-kernel@vger.kernel.org,
acme@infradead.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 9/9] perf, tools: Add a --quiet flag to perf list
Date: Sun, 15 Jun 2014 22:17:41 +0900 [thread overview]
Message-ID: <1402838261.1684.39.camel@leonhard> (raw)
In-Reply-To: <1402700580-26939-10-git-send-email-andi@firstfloor.org>
Hi Andi,
2014-06-13 (금), 16:03 -0700, Andi Kleen:
> From: Andi Kleen <ak@linux.intel.com>
>
> Add a --quiet flag to perf list to not print the event descriptions
> that were earlier added for JSON events. This may be useful to
> get a less crowded listing.
>
> It's still default to print descriptions as that is the more useful
> default for most users. Requested by Namhyung Kim.
Did I request the --quiet thing? It seems like there's a
miscommunication.. :-/
I still prefer -v option and not printing descriptions by default - but
want to inform users to use -v option. However I also want to hear from
others on this.
Btw, it'd better if it can support event glob on the pmu events (or
simply all events) too as this will increase the number of events
significantly. But this can be a further work.
Thanks,
Namhyung
>
> Before:
>
> % perf list
> ...
> baclears.any [Counts the total number when the front end is
> resteered, mainly when the BPU cannot provide a
> correct prediction and this is corrected by other
> branch handling mechanisms at the front end]
> br_inst_exec.all_branches [Speculative and retired branches]
>
> After:
>
> % perf list --quiet
> ...
> baclears.any [Kernel PMU event]
> br_inst_exec.all_branches [Kernel PMU event]
next prev parent reply other threads:[~2014-06-15 13:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 23:02 perf: Add support for full Intel event lists v6 Andi Kleen
2014-06-13 23:02 ` [PATCH 1/9] perf, tools: Add jsmn `jasmine' JSON parser v3 Andi Kleen
2014-06-13 23:02 ` [PATCH 2/9] perf, tools: Add support for text descriptions of events and alias add Andi Kleen
2014-06-13 23:02 ` [PATCH 3/9] perf, tools: Add support for reading JSON event files v3 Andi Kleen
2014-06-13 23:02 ` [PATCH 4/9] perf, tools: Automatically look for event file name for cpu v3 Andi Kleen
2014-07-09 2:13 ` Sukadev Bhattiprolu
2014-07-09 4:07 ` Andi Kleen
2014-06-13 23:02 ` [PATCH 5/9] perf, tools: Add perf download to download event files v4 Andi Kleen
2014-06-13 23:02 ` [PATCH 6/9] perf, tools: Allow events with dot Andi Kleen
2014-06-13 23:02 ` [PATCH 7/9] perf, tools: Query terminal width and use in perf list Andi Kleen
2014-06-13 23:02 ` [PATCH 8/9] perf, tools, test: Add test case for alias and JSON parsing v2 Andi Kleen
2014-06-13 23:03 ` [PATCH 9/9] perf, tools: Add a --quiet flag to perf list Andi Kleen
2014-06-15 13:17 ` Namhyung Kim [this message]
2014-06-15 16:11 ` Andi Kleen
2014-06-18 0:36 ` Namhyung Kim
2014-07-09 22:20 ` Jiri Olsa
2014-06-14 20:49 ` perf: Add support for full Intel event lists v6 Hagen Paul Pfeifer
2014-06-14 21:28 ` Andi Kleen
2014-06-15 13:03 ` Namhyung Kim
2014-06-15 16:09 ` Andi Kleen
2014-06-16 8:20 ` Hagen Paul Pfeifer
-- strict thread matches above, loose matches on Subject: below --
2014-06-27 23:15 perf: Add support for full Intel event lists v7 Andi Kleen
2014-06-27 23:16 ` [PATCH 9/9] perf, tools: Add a --quiet flag to perf list Andi Kleen
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=1402838261.1684.39.camel@leonhard \
--to=namhyung@kernel.org \
--cc=acme@infradead.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.