From: Namhyung Kim <namhyung@gmail.com>
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: Wed, 18 Jun 2014 09:36:12 +0900 [thread overview]
Message-ID: <87k38f835v.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140615161138.GH5714@two.firstfloor.org> (Andi Kleen's message of "Sun, 15 Jun 2014 18:11:38 +0200")
Hi Andi,
On Sun, 15 Jun 2014 18:11:38 +0200, Andi Kleen wrote:
> On Sun, Jun 15, 2014 at 10:17:41PM +0900, Namhyung Kim wrote:
>> > 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.. :-/
>
> Well it was done based on your feedback, and gets the closest
> to your original request as possible.
>
>> 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.
>
> That already works.
Oh, didn't notice that. Nice work! :)
Thanks,
Namhyung
>
> % perf list icache*
> List of pre-defined events (to be used in -e):
> icache.ifetch_stall [Cycles where a code-fetch
> stalled due to L1
> instruction-cache miss
> or an iTLB miss]
> icache.misses [Number of Instruction
> Cache, Streaming Buffer
> and Victim Cache
> Misses. Includes
> Uncacheable accesses]
> %
>
> -Andi
next prev parent reply other threads:[~2014-06-18 0:36 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
2014-06-15 16:11 ` Andi Kleen
2014-06-18 0:36 ` Namhyung Kim [this message]
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
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=87k38f835v.fsf@sejong.aot.lge.com \
--to=namhyung@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome