From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Cc: acme@redhat.com, mingo@elte.hu, paulus@samba.org,
cjashfor@linux.vnet.ibm.com, fweisbec@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] perf, tool: Add new event group management
Date: Tue, 10 Apr 2012 15:19:47 +0200 [thread overview]
Message-ID: <20120410131947.GC1650@m.brq.redhat.com> (raw)
In-Reply-To: <1332269081.18960.444.camel@twins>
On Tue, Mar 20, 2012 at 07:44:41PM +0100, Peter Zijlstra wrote:
> On Tue, 2012-03-20 at 19:15 +0100, Jiri Olsa wrote:
> > Examples (first event in brackets is group leader):
> >
> > # 1 group (cpu-clock,task-clock)
> > perf record --group -e cpu-clock,task-clock ls
> > perf record --group parsed -e cpu-clock,task-clock ls
> >
> > # 2 groups (cpu-clock,task-clock) (minor-faults,major-faults)
> > perf record --group parsed -e cpu-clock,task-clock \
> > -e minor-faults,major-faults ls
> >
> > # 1 group (cpu-clock,task-clock,minor-faults,major-faults)
> > perf record --group -e cpu-clock,task-clock \
> > -e minor-faults,major-faults ls
> >
> > # 2 groups (cpu-clock,task-clock) (minor-faults,major-faults)
> > perf record --group parsed -e cpu-clock,task-clock \
> > -e minor-faults,major-faults -e instructions ls
> >
> > # 1 group (cpu-clock,task-clock,minor-faults,major-faults,instructions)
> > perf record --group -e cpu-clock,task-clock \
> > -e minor-faults,major-faults -e instructions ls
>
> I can't help but dislike the --group/--group parsed thing...
>
> How about something like:
>
> event_group = "{", events, "}" , [ ":", event_group_mod ]
>
> Such that you can write things like:
>
> perf record -e "{cpu-clock,cache-misses,cache-references}"
>
> perf stat -e "{cpu-clock,cycles},{cpu-clock,cache-misses,cache-references}"
> perf stat -e "{cpu-clock,cycles}" -e "{cpu-clock,cache-misses,cache-references}"
>
> I'm not sure what the current behaviour of --group is, if you create a
> group like this, do they all sample?
>
> If so, we need some option like:
>
> perf record -e "{cpu-clock,cache-misses,cache-references}:1"
>
> to mean, only sample on cpu-clock but use PERF_SAMPLE_READ and
> PERF_FORMAT_GROUP to read all siblings on every cpu-clock sample.
hi,
I'm looking on how to present this data in perf and it seems we need
to reset all siblings once we read/store them (in kernel) to the leader
sample.
My current thinking is to store siblings' sum values for each
hists entry of the sample (perf report count unit) .. and display
them in similar way we display callchains: for each hists entry
display the sum value for each sibling.
Could you provide more of your world examples? Your expectations about
presenting this..
Maybe we want to make the reset optional, and do some do some other
math with siblings' values..?
Thoughts? ;)
thanks,
jirka
next prev parent reply other threads:[~2012-04-10 13:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:15 [RFC 0/3] perf tool: Add new event group management Jiri Olsa
2012-03-20 18:15 ` [PATCH 1/3] perf, tool: Fix various casting issues for 32 bits Jiri Olsa
2012-03-23 8:29 ` [tip:perf/urgent] perf tools: " tip-bot for Jiri Olsa
2012-03-20 18:15 ` [PATCH 2/3] perf, tool: Fix modifier to be applied on correct events Jiri Olsa
2012-03-23 8:30 ` [tip:perf/urgent] perf tools: " tip-bot for Jiri Olsa
2012-03-20 18:15 ` [PATCH 3/3] perf, tool: Add new event group management Jiri Olsa
2012-03-20 18:44 ` Peter Zijlstra
2012-03-20 20:46 ` Ingo Molnar
2012-03-20 22:18 ` Arnaldo Carvalho de Melo
2012-03-21 9:15 ` Peter Zijlstra
2012-03-21 9:52 ` Ingo Molnar
2012-03-21 11:54 ` Peter Zijlstra
2012-03-21 12:15 ` Ingo Molnar
2012-03-21 15:13 ` Arnaldo Carvalho de Melo
2012-03-22 7:56 ` Ingo Molnar
2012-03-22 12:41 ` Arnaldo Carvalho de Melo
2012-03-22 13:54 ` Ingo Molnar
2012-03-22 14:07 ` Jiri Olsa
2012-03-20 22:36 ` Jiri Olsa
2012-03-21 11:54 ` Peter Zijlstra
2012-03-21 10:42 ` Jiri Olsa
2012-03-21 15:11 ` Arnaldo Carvalho de Melo
2012-03-21 22:27 ` Jiri Olsa
2012-03-22 12:40 ` Arnaldo Carvalho de Melo
2012-04-10 13:19 ` Jiri Olsa [this message]
2012-03-20 20:08 ` Arnaldo Carvalho de Melo
2012-03-20 22:16 ` Jiri Olsa
2012-03-21 2:12 ` Namhyung Kim
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=20120410131947.GC1650@m.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.