From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Lin Ming <ming.m.lin@intel.com>
Cc: "mingo@elte.hu" <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Matt Fleming <matt@console-pimps.org>
Subject: Re: [RFC] perf: EBNF for event syntax
Date: Fri, 25 Mar 2011 15:17:15 +0100 [thread overview]
Message-ID: <1301062635.2250.212.camel@laptop> (raw)
In-Reply-To: <1301060121.2269.1.camel@localhost>
On Fri, 2011-03-25 at 21:35 +0800, Lin Ming wrote:
> > There was a suggestion a while back to make:
> >
> > -e ev1,ev2,ev3
> >
> > create an event group with ev2 and ev3 siblings of ev1, and have
> > multiple -e instances create separate counters.
> >
> > The problem is that its not backwards compatible, but something like
> > that would still be very nice to have.
>
> Currently, it means a list of independent events, right?
>
Right, and as said changing this would create some backward compat
problems so I'm not sure its the best proposal, just wanted to raise the
issue that such functionality would be nice.
next prev parent reply other threads:[~2011-03-25 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 3:36 [RFC] perf: EBNF for event syntax Lin Ming
2011-03-25 11:07 ` Peter Zijlstra
2011-03-25 13:35 ` Lin Ming
2011-03-25 14:17 ` Peter Zijlstra [this message]
2011-03-26 20:48 ` Ulrich Drepper
2011-03-28 5:40 ` Masami Hiramatsu
2011-03-28 7:58 ` Peter Zijlstra
2011-03-28 8:52 ` Matt Fleming
2011-03-28 10:12 ` Masami Hiramatsu
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=1301062635.2250.212.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=matt@console-pimps.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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