From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephane Eranian <eranian@google.com>
Cc: Lin Ming <ming.m.lin@intel.com>, Ingo Molnar <mingo@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
"robert.richter@amd.com" <robert.richter@amd.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
"paulus@samba.org" <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [DRAFT PATCH 2/3] perf: Implement Nehalem uncore pmu
Date: Thu, 04 Nov 2010 20:28:49 +0100 [thread overview]
Message-ID: <1288898929.2039.78.camel@laptop> (raw)
In-Reply-To: <AANLkTi=GVVWxOpZ9Gorn4_r2tASAqOV5+BT7o92xrwJJ@mail.gmail.com>
On Tue, 2010-11-02 at 17:59 +0100, Stephane Eranian wrote:
> I think using uncore PMU to measure per-thread is pretty much useless.
> Maybe it should not even be allowed. There is no way you can correlate
> the counts you're getting to a place in your program. Or put differently,
> sampling in per-thread mode using uncore is useless.
Right, per-task uncore event should not be allowed. I think it as simple
as setting pmu::task_ctx_nr = perf_invalid_context.
next prev parent reply other threads:[~2010-11-04 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 7:28 [DRAFT PATCH 2/3] perf: Implement Nehalem uncore pmu Lin Ming
2010-11-02 14:53 ` Stephane Eranian
2010-11-02 15:33 ` Lin Ming
2010-11-02 16:59 ` Stephane Eranian
2010-11-04 19:28 ` Peter Zijlstra [this message]
2010-11-05 1:30 ` Lin Ming
2010-11-08 12:20 ` Andi Kleen
2010-11-09 5:01 ` Lin Ming
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=1288898929.2039.78.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=robert.richter@amd.com \
--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.