From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: eranian@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Robert Richter <robert.richter@amd.com>,
Paul Mackerras <paulus@samba.org>,
Andi Kleen <andi@firstfloor.org>,
Maynard Johnson <mpjohn@us.ibm.com>, Carl Love <cel@us.ibm.com>,
Corey J Ashford <cjashfor@us.ibm.com>,
Philip Mucci <mucci@eecs.utk.edu>,
Dan Terpstra <terpstra@eecs.utk.edu>,
perfmon2-devel <perfmon2-devel@lists.sourceforge.net>
Subject: Re: perf_counters issue with PERF_SAMPLE_GROUP
Date: Wed, 12 Aug 2009 11:02:34 +0200 [thread overview]
Message-ID: <20090812090234.GB14114@elte.hu> (raw)
In-Reply-To: <1250065963.10001.30.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Tue, 2009-08-11 at 23:08 +0200, stephane eranian wrote:
>
> > But aren't you going to change the cpu, pid target stuff we
> > discussed a couple of weeks ago anyway?
>
> Right, I'd like to, but Ingo doesn't. I haven't heard back from
> Paul on this.
Not sure we want to change it. Mixing PID and CPU into the same
space disallows the simultaneous application of both. I.e. right now
we allow 3 models:
- PID-ish
- CPU-ish
- PID and CPU [say measure CPU#2 component of an inherited workload.]
Also, i dont really see the use-cases for new targets. (i've seen a
few mentioned but none seemed valid) What new targets do people have
in mind?
Ingo
next prev parent reply other threads:[~2009-08-12 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 15:41 stephane eranian
2009-08-11 16:05 ` Peter Zijlstra
2009-08-11 19:40 ` stephane eranian
2009-08-11 20:55 ` Peter Zijlstra
2009-08-11 21:08 ` stephane eranian
2009-08-12 8:32 ` Peter Zijlstra
2009-08-12 9:02 ` Ingo Molnar [this message]
2009-08-12 12:22 ` stephane eranian
2009-08-13 9:46 ` Ingo Molnar
2009-08-13 19:15 ` stephane eranian
2009-08-13 23:13 ` Corey Ashford
2009-08-13 23:49 ` Paul Mackerras
2009-08-12 20:54 ` stephane eranian
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=20090812090234.GB14114@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cel@us.ibm.com \
--cc=cjashfor@us.ibm.com \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpjohn@us.ibm.com \
--cc=mucci@eecs.utk.edu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sourceforge.net \
--cc=robert.richter@amd.com \
--cc=terpstra@eecs.utk.edu \
--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
all inboxes | Powered by JetHome®