From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
mingo@elte.hu, paulus@samba.org, cjashfor@linux.vnet.ibm.com,
fweisbec@gmail.com, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/3] perf, tool: Add new event group management
Date: Wed, 21 Mar 2012 12:11:19 -0300 [thread overview]
Message-ID: <20120321151119.GC21163@infradead.org> (raw)
In-Reply-To: <20120321104214.GB1632@m.brq.redhat.com>
Em Wed, Mar 21, 2012 at 11:42:14AM +0100, Jiri Olsa escreveu:
> On Tue, Mar 20, 2012 at 07:44:41PM +0100, Peter Zijlstra wrote:
> > 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.
> >
> > Now the disadvantage is that {} needs quotes on bash, the advantage is
> > that its completely natural on how to construct groups, without weird
> > --group/--group parsed. Also it provides a place for group modifiers.
>
> how about '=group' keyword followed by ':' modifier
> perf record -e "cpu-clock,cache-misses,cache-references=group:1"
>
> or '=$groupname' and use the group name in output like
> perf stat -e "task-clock,context-switches=krava:1" ls
>
> Performance counter stats for 'ls':
>
> 1.003695 task-clock/krava # 0.083 CPUs utilized
> 0 context-switches/krava # 0.000 K/sec
>
Humm, interesting, perhaps putting the group name before the =event_list
will be more intuitive?
I.e.:
perf stat -e "krava=task-clock,context-switches:1" ls
- Arnaldo
next prev parent reply other threads:[~2012-03-21 15:12 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 [this message]
2012-03-21 22:27 ` Jiri Olsa
2012-03-22 12:40 ` Arnaldo Carvalho de Melo
2012-04-10 13:19 ` Jiri Olsa
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=20120321151119.GC21163@infradead.org \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.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 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).