linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>,
	Stephane Eranian <eranian@google.com>,
	Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCHSET 0/8] perf tools: Support multiple keys in a single hierarchy level (v1)
Date: Thu, 3 Mar 2016 08:16:36 +0900	[thread overview]
Message-ID: <20160302231636.GA19162@sejong> (raw)
In-Reply-To: <20160302162507.GT3604@kernel.org>

Hi Arnaldo,

On Wed, Mar 02, 2016 at 01:25:07PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Mar 03, 2016 at 01:12:00AM +0900, Namhyung Kim escreveu:
> > Hello,
> > 
> > This implements what Arnaldo suggested in previous discussion of
> > hierarchy patchset [1].  Originally each level in a hierarchy can have
> > a single sort key in it, but with patches it's possible to have more
> > than one sort keys.  I added the struct perf_hpp_list_node and carry
> > it to group output formats (hpp_fmt) in a single level.
> > 
> > I used ':' character instead of '+' as suggested since the '+' was
> > also used to extend existing sort keys (like -s '+cpu').
> 
> Could we use ';' instead? That is associated with lists as well, i.e.:
> 
>   perf report --hierarchy -s prev_pid;prev_comm,next_pid;next_comm
> 
> What do you think? Others?

The ';' is interpreted by shell first, so it needs to be quoted.

  $ perf report -s comm,dso;sym
  bash: sym: command not found

Thanks,
Namhyung


> 
> But anyway, thanks for working on this, I'll try and test it,
> 
> - Arnaldo
>  
> > Example below shows how 4 sort keys are used for 2 levels.  As you can
> > see, the first level shows pid and comm of previous (switched) task
> > and the second level shows pid and comm of next task.
> > 
> >   $ perf report --hierarchy -s prev_pid:prev_comm,next_pid:next_comm \
> >    --percent-limit 1 -i perf.data.sched
> >   ...
> >   #    Overhead  prev_pid+prev_comm / next_pid+next_comm
> >   # ...........  .......................................
> >   #
> >       22.36%     0  swapper/0
> >           9.48%     17773  transmission-gt
> >           5.25%     109  kworker/0:1H
> >           1.53%     6524  Xephyr
> >       21.39%     17773  transmission-gt
> >           9.52%     0  swapper/0
> >           9.04%     0  swapper/2
> >           1.78%     0  swapper/3
> > 
> > 
> > It's available on the 'perf/hierarchy-multi-v1' branch in my tree
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
> > 
> > 
> > Any feedbacks are welcome
> > 
> > Thanks,
> > Namhyung
> > 
> > 
> > [1] https://lkml.org/lkml/2016/2/24/1041
> > 
> > 
> > Namhyung Kim (8):
> >   perf tools: Add level field to struct perf_hpp_fmt
> >   perf tools: Introduce perf_hpp__setup_hists_formats()
> >   perf tools: Use own hpp_list for hierarchy mode
> >   perf tools: Support multiple sort keys in a hierarchy
> >   perf tools: Fix indent for multiple hierarchy sort key
> >   perf report: Use hierarchy hpp list on stdio
> >   perf hists browser: Use hierarchy hpp list
> >   perf report: Use hierarchy hpp list on gtk
> > 
> >  tools/perf/ui/browsers/hists.c | 147 +++++++++++++++++++----------------
> >  tools/perf/ui/gtk/hists.c      |  73 +++++++++++-------
> >  tools/perf/ui/hist.c           |  67 ++++++++++++++++
> >  tools/perf/ui/stdio/hist.c     | 171 +++++++++++++++++++++--------------------
> >  tools/perf/util/hist.c         |  81 +++++++++++++------
> >  tools/perf/util/hist.h         |  12 +++
> >  tools/perf/util/sort.c         | 123 ++++++++++++++++++++---------
> >  tools/perf/util/sort.h         |   1 +
> >  8 files changed, 438 insertions(+), 237 deletions(-)
> > 
> > -- 
> > 2.7.1

  reply	other threads:[~2016-03-02 23:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 16:12 [PATCHSET 0/8] perf tools: Support multiple keys in a single hierarchy level (v1) Namhyung Kim
2016-03-02 16:12 ` [PATCH 1/8] perf tools: Add level field to struct perf_hpp_fmt Namhyung Kim
2016-03-02 16:12 ` [PATCH 2/8] perf tools: Introduce perf_hpp__setup_hists_formats() Namhyung Kim
2016-03-03 13:40   ` Jiri Olsa
2016-03-03 23:52     ` Namhyung Kim
2016-03-03 13:40   ` Jiri Olsa
2016-03-03 23:53     ` Namhyung Kim
2016-03-02 16:12 ` [PATCH 3/8] perf tools: Use own hpp_list for hierarchy mode Namhyung Kim
2016-03-02 16:12 ` [PATCH 4/8] perf tools: Support multiple sort keys in a hierarchy Namhyung Kim
2016-03-02 16:12 ` [PATCH 5/8] perf tools: Fix indent for multiple hierarchy sort key Namhyung Kim
2016-03-02 16:12 ` [PATCH 6/8] perf report: Use hierarchy hpp list on stdio Namhyung Kim
2016-03-02 16:12 ` [PATCH 7/8] perf hists browser: Use hierarchy hpp list Namhyung Kim
2016-03-02 16:12 ` [PATCH 8/8] perf report: Use hierarchy hpp list on gtk Namhyung Kim
2016-03-02 16:25 ` [PATCHSET 0/8] perf tools: Support multiple keys in a single hierarchy level (v1) Arnaldo Carvalho de Melo
2016-03-02 23:16   ` Namhyung Kim [this message]
2016-03-03 13:08     ` [RFC] " Arnaldo Carvalho de Melo
2016-03-03 23:50       ` Namhyung Kim
2016-03-04 13:32         ` Arnaldo Carvalho de Melo

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=20160302231636.GA19162@sejong \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=wangnan0@huawei.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;
as well as URLs for NNTP newsgroup(s).