From: Andi Kleen <ak@linux•intel.com>
To: Jiri Olsa <jolsa@redhat•com>
Cc: Sukadev Bhattiprolu <sukadev@linux•vnet.ibm.com>,
mingo@redhat•com, Michael Ellerman <mpe@ellerman•id.au>,
Arnaldo Carvalho de Melo <acme@kernel•org>,
Paul Mackerras <paulus@samba•org>,
namhyung@kernel•org, linuxppc-dev@lists•ozlabs.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH 09/10] perf, tools: Add a --no-desc flag to perf list
Date: Thu, 28 May 2015 11:07:05 -0700 [thread overview]
Message-ID: <20150528180705.GQ7484@tassilo.jf.intel.com> (raw)
In-Reply-To: <20150528123914.GJ12392@krava.redhat.com>
On Thu, May 28, 2015 at 02:39:14PM +0200, Jiri Olsa wrote:
> On Wed, May 27, 2015 at 02:23:28PM -0700, Sukadev Bhattiprolu wrote:
> > From: Andi Kleen <ak@linux•intel.com>
> >
> > Add a --no-desc 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.
>
> I might not be typical user, but the first thing I tried to
> explore was 'perf list -v' ;-)
>
> would it be better to have just the list with event names for:
> $ perf list
>
> and with descriptions for:
> $ perf list -v
>
> not sure we already discussed this..
It was discussed last time. I think it's better to have descriptions
by default. Far more user friendly.
One thing we could in theory do with -v is to switch between Brief and Public
Description (the later is often more verbose). Would need some changes
to the alias code to have two descriptions though.
-Andi
--
ak@linux•intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-05-28 18:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:23 [PATCH 0/10] perf: Add support for PMU events in JSON format Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 01/10] perf, tools: Add jsmn `jasmine' JSON parser Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 02/10] jevents: Program to convert JSON file to C style file Sukadev Bhattiprolu
2015-05-28 12:06 ` Jiri Olsa
2015-05-28 12:09 ` Jiri Olsa
2015-05-27 21:23 ` [PATCH 03/10] Use pmu_events_map table to create event aliases Sukadev Bhattiprolu
2015-05-28 12:46 ` Jiri Olsa
2015-05-27 21:23 ` [PATCH 04/10] perf, tools: Handle header line in mapfile Sukadev Bhattiprolu
2015-05-28 12:42 ` Jiri Olsa
2015-05-29 5:45 ` Sukadev Bhattiprolu
2015-05-29 9:13 ` Jiri Olsa
2015-05-30 5:49 ` Andi Kleen
2015-06-01 10:01 ` Jiri Olsa
2015-05-27 21:23 ` [PATCH 05/10] perf, tools: Allow events with dot Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 06/10] perf, tools: Support CPU id matching for x86 v2 Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 07/10] perf, tools: Support alias descriptions Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 08/10] perf, tools: Query terminal width and use in perf list Sukadev Bhattiprolu
2015-05-27 21:23 ` [PATCH 09/10] perf, tools: Add a --no-desc flag to " Sukadev Bhattiprolu
2015-05-28 12:39 ` Jiri Olsa
2015-05-28 18:07 ` Andi Kleen [this message]
2015-05-27 21:23 ` [PATCH 10/10] perf: Add power8 PMU events in JSON format Sukadev Bhattiprolu
2015-05-28 11:42 ` [PATCH 0/10] perf: Add support for " Jiri Olsa
2015-05-28 12:43 ` Jiri Olsa
2015-05-28 11:43 ` Jiri Olsa
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=20150528180705.GQ7484@tassilo.jf.intel.com \
--to=ak@linux$(echo .)intel.com \
--cc=acme@kernel$(echo .)org \
--cc=jolsa@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@redhat$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=namhyung@kernel$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=sukadev@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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