[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1402838261.1684.39.camel@leonhard>
Date: Sun, 15 Jun 2014 22:17:41 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: jolsa@...hat.com, linux-kernel@...r.kernel.org, acme@...radead.org,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 9/9] perf, tools: Add a --quiet flag to perf list
Hi Andi,
2014-06-13 (금), 16:03 -0700, Andi Kleen:
> From: Andi Kleen <ak@...ux.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]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists