The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com,
	Linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v3 1/3] perf report: Change sort order by a specified event in group
Date: Tue, 17 Dec 2019 10:06:00 +0100	[thread overview]
Message-ID: <20191217090600.GA24766@krava> (raw)
In-Reply-To: <fcedac74-7fb4-1c3b-67a3-9af24c256f40@linux.intel.com>

On Tue, Dec 17, 2019 at 09:47:01AM +0800, Jin, Yao wrote:
> 
> 
> On 12/16/2019 3:31 PM, Jiri Olsa wrote:
> > On Thu, Dec 12, 2019 at 08:33:35PM +0800, Jin Yao wrote:
> > 
> > SNIP
> > 
> > > 
> > > Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> > > ---
> > >   tools/perf/Documentation/perf-report.txt |   4 +
> > >   tools/perf/builtin-report.c              |  10 +++
> > >   tools/perf/ui/hist.c                     | 108 +++++++++++++++++++----
> > >   tools/perf/util/symbol_conf.h            |   1 +
> > >   4 files changed, 108 insertions(+), 15 deletions(-)
> > > 
> > > diff --git a/tools/perf/Documentation/perf-report.txt b/tools/perf/Documentation/perf-report.txt
> > > index 8dbe2119686a..9ade613ef020 100644
> > > --- a/tools/perf/Documentation/perf-report.txt
> > > +++ b/tools/perf/Documentation/perf-report.txt
> > > @@ -371,6 +371,10 @@ OPTIONS
> > >   	Show event group information together. It forces group output also
> > >   	if there are no groups defined in data file.
> > > +--group-sort-idx::
> > > +	Sort the output by the event at the index n in group. If n is invalid,
> > > +	sort by the first event. WARNING: This should be used with --group.
> > 
> > --group in record or report?
> > 
> 
> This --group is in perf-report. So even if it's not created with -e '{}' in
> perf-record, it still supports to show event information together.
> 
> > you can also create groups with -e '{}', not just --group option
> > 
> > I wonder you could check early on 'evlist->nr_groups' and fail
> > if there's no group defined if the option is enabled
> > 
> 
> Maybe we don't need to check that because it supports the case of no group
> defined.
> 
> For example,
> perf record -e cycles,instructions
> perf report --group --group-sort-idx 1 --stdio

hum, --group will force evlist->nr_groups == 1, right?

so we could warn/fail on (group-sort-idx && !evlist->nr_groups)


SNIP

> 
> Thanks. Can we say something as following?
> 
> --group-sort-idx::
> 	Sort the output by the event at the index n in group. If n is invalid, sort
> by the first event. It can support multiple groups with different amount of
> events. WARNING: This should be used with perf report --group.

if the events are already grouped you dont need --group ;-) how about:

	This should be used on grouped events.

thanks,
jirka


  reply	other threads:[~2019-12-17  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 12:33 [PATCH v3 1/3] perf report: Change sort order by a specified event in group Jin Yao
2019-12-12 12:33 ` [PATCH v3 2/3] perf report: Support a new key to reload the browser Jin Yao
2019-12-12 12:33 ` [PATCH v3 3/3] perf report: support hotkey to let user select any event for sorting Jin Yao
2019-12-16  7:31 ` [PATCH v3 1/3] perf report: Change sort order by a specified event in group Jiri Olsa
2019-12-17  1:47   ` Jin, Yao
2019-12-17  9:06     ` Jiri Olsa [this message]
2019-12-18  2:29       ` Jin, Yao

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=20191217090600.GA24766@krava \
    --to=jolsa@redhat.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    /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