From: Jiri Olsa <jolsa@redhat.com>
To: Don Zickus <dzickus@redhat.com>
Cc: acme@kernel.org, namhyung@kernel.org, eranian@google.com,
Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 5/5] perf: Enable multiple hist_entry_group output
Date: Fri, 11 Apr 2014 19:30:00 +0200 [thread overview]
Message-ID: <20140411173000.GC22707@krava.brq.redhat.com> (raw)
In-Reply-To: <1397160661-33395-6-git-send-email-dzickus@redhat.com>
On Thu, Apr 10, 2014 at 04:11:01PM -0400, Don Zickus wrote:
> Enable multiple hist_entry_group groups in the output based on a sort
> method.
>
> Currently only 'perf report' is hooked in with '--group-sort='. The choices
> are cpu, pid, and cacheline. Only --stdio works right now. I haven't figured
> out how the other outputs work.
>
> Sample output from 'perf mem record -a grep -r foo /* > /dev/null'
>
> (normal) perf mem report --percent-limit=1.0 --stdio
>
> Overhead Samples
> Local Weight Memory access Symbol
> ........ ............ ............ ........................ ........................
>
> 4.13% 1 1759 Uncached hit [k] ahci_scr_read
> 1.16% 1 492 L1 hit [k] _raw_read_lock
>
> (cpu groups) perf mem report --group-sort=cpu --percent-limit=1.0 --stdio
>
> Overhead Samples CPU
> Local Weight Memory access Symbol
> ........ ............ ............ ........................ ........................
>
> 28.80% 1239 25
> 3.07% 377 L1 hit [k] complete_walk
> 2.76% 339 LFB hit [k] update_cfs_shares
> 2.66% 326 LFB hit [k] copy_user_enhanced_f
> 2.11% 259 Local RAM hit [k] copy_user_enhanced_f
> 1.84% 226 LFB hit [k] copy_user_enhanced_f
> 1.74% 213 LFB hit [k] copy_user_enhanced_f
> 1.53% 187 LFB hit [k] copy_user_enhanced_f
> 1.04% 128 LFB hit [k] copy_user_enhanced_f
> 1.01% 124 LFB hit [k] copy_user_enhanced_f
> 27.44% 990 7
> 15.06% 1759 Uncached hit [k] ahci_scr_read
> 4.21% 492 L1 hit [k] _raw_read_lock
> 1.04% 122 LFB hit [k] find_busiest_group
> 1.02% 1 7 L1 hit [.] __gconv_transform_ut
> 20.34% 1010 0
> 4.04% 5 7 L1 hit [k] poll_idle
> 3.56% 308 Local RAM hit [k] copy_user_enhanced_f
> 2.59% 224 L3 hit [k] copy_user_enhanced_f
> 2.12% 184 Local RAM hit [k] copy_user_enhanced_f
> 1.54% 1 7 L1 hit [.] __gconv_transform_ut
nice, that looks very usefull
Correct me if I'm wrong, but your current design allows to define
just one group, right?
so, current code can do following CPU sorting:
Overhead CPU
........ ...
90% 0
10% 1
and with your changes we could do:
Overhead CPU symbol
........ ... ......
90% 0
50% krava1
20% krava2
30% krava3
10% 1
50% krava4
50% krava5
I wonder we could go more generic and allow more nested groups,
like eg allow group sort on cpu and pid (or more):
Overhead CPU pid symbol
........ ... ... ......
90% 0
50% 100
50% krava1
20% krava2
30% krava3
50% 110
50% krava1
20% krava2
30% krava3
10% 1
100% 200
50% krava4
50% krava5
I glanced over the changes and I wonder we could do it
by chaining hists structs via 'struct hist_entry'
like adding 'struct hists' into 'struct hists_entry'
and making the sort_order local for each 'struct hists'
just first thoughts.. need to look at it closely ;-)
jirka
next prev parent reply other threads:[~2014-04-11 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 20:10 [RFC 0/5] perf: Create hist_entry groups Don Zickus
2014-04-10 20:10 ` [RFC 1/5] perf: Wrap __hists__add_entry to prep for group entry change Don Zickus
2014-04-10 20:10 ` [RFC 2/5] perf: Use macros to walk hist entries Don Zickus
2014-04-10 20:10 ` [RFC 3/5] perf: Add in stub hist_entry_group code Don Zickus
2014-04-10 20:11 ` [RFC 4/5] perf: Switch to using hist_entry_group Don Zickus
2014-04-10 20:11 ` [RFC 5/5] perf: Enable multiple hist_entry_group output Don Zickus
2014-04-11 17:30 ` Jiri Olsa [this message]
2014-04-11 18:28 ` Don Zickus
2014-04-11 18:34 ` Don Zickus
2014-04-14 9:19 ` Jiri Olsa
2014-04-14 14:13 ` Don Zickus
2014-04-15 3:01 ` [RFC 0/5] perf: Create hist_entry groups Namhyung Kim
2014-04-15 9:40 ` Jiri Olsa
2014-04-15 11:35 ` Namhyung Kim
2014-04-15 16:08 ` Don Zickus
2014-04-16 8:29 ` Namhyung Kim
2014-04-21 20:07 ` Don Zickus
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=20140411173000.GC22707@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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