From: Matt Fleming <matt@console-pimps.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Lin Ming <ming.m.lin@intel.com>,
mingo@elte.hu, Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
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>,
"2nddept-manager@sdl.hitachi.co.jp"
<2nddept-manager@sdl.hitachi.co.jp>
Subject: Re: [RFC] perf: EBNF for event syntax
Date: Mon, 28 Mar 2011 09:52:23 +0100 [thread overview]
Message-ID: <20110328095223.76e4debe@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1301299090.4859.6.camel@twins>
On Mon, 28 Mar 2011 09:58:10 +0200
Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> Groups are most useful in measuring events on another base, which is
> basically mandatory if your primary event doesn't have sampling
> support itself.
Just FYI...
When I was looking at group event support for SH (because the hardware
doesn't have sampling support) I was trying to avoid the user being
required to setup the groups on the command-line, e.g. I wrote it so
that the group event creation was all done "behind the scenes".
For those architectures/platforms that are missing sampling support I
still think that group event creation should be as invisible as
possible.
next prev parent reply other threads:[~2011-03-28 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 3:36 Lin Ming
2011-03-25 11:07 ` Peter Zijlstra
2011-03-25 13:35 ` Lin Ming
2011-03-25 14:17 ` Peter Zijlstra
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 [this message]
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=20110328095223.76e4debe@mfleming-mobl1.ger.corp.intel.com \
--to=matt@console-pimps.org \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=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=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
Powered by JetHome