From: Lin Ming <ming.m.lin@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: Don Zickus <dzickus@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
lkml <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [RFC PATCH 2/3 v2] perf: Implement Nehalem uncore pmu
Date: Thu, 02 Dec 2010 13:26:39 +0800 [thread overview]
Message-ID: <1291267599.2405.318.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <AANLkTi=qDsNwVAoHF=x62C8x=x3cGaobTZNDGHDr8YZ+@mail.gmail.com>
On Wed, 2010-12-01 at 21:04 +0800, Stephane Eranian wrote:
> On Wed, Dec 1, 2010 at 4:21 AM, Lin Ming <ming.m.lin@intel.com> wrote:
> >
> > On Fri, 2010-11-26 at 18:06 +0800, Stephane Eranian wrote:
> > > On Fri, Nov 26, 2010 at 10:00 AM, Lin Ming <lin@ming.vg> wrote:
> > > > On Fri, Nov 26, 2010 at 4:33 PM, Stephane Eranian <eranian@google.com> wrote:
> > > >> Lin,
> > > >>
> > > >> Looked at the perfmon code, and it seems the mask is actual
> > > >> cores, not threads:
> > > >> rdmsrl(MSR_NHM_UNC_GLOBAL_CTRL, val);
> > > >> val |= 1ULL << (48 + cpu_data(smp_processor_id()).cpu_core_id);
> > > >> wrmsrl(MSR_NHM_UNC_GLOBAL_CTRL, val);
> > > >>
> > > >> That seems to imply both threads will get the interrupt.
> > > >>
> > > >> In the the overflowed event was programmed from on of the two threads, that
> > > >> means one will process the overflow, the other will get spurious.
> > > >>
> > > >> On the cores where no uncore was programmed, then both threads will have
> > > >> a spurious interrupt.
> > > >
> > > > But in my test, if HT is on, only the 2 theads in one of the four cores
> > > > will receive the interrupt. Even worse, we don't know which core will
> > > > receive the interrupt
> > > > when overflow happens.
> > > >
> > > The MSR_NHM_UNC_GLOBAL_CTRL is per socket not per core.
> >
> > Understood.
> >
> > >
> > > > I'll do more tests to verify this.
> > >
> > > In your tests, are your programming the same uncore event
> > > across all CPUs? If so then you may have a race condition
> > > setting the MSR because it read-modify-write.
> > >
> > > What about you program only one uncore event from one CPU?
> >
> > This is what I tested, programming only one uncore event from one CPU.
>
> > When HT is off, all four cores in the socket receive the interrupt.
>
> If the value of the MSR is 0xf << 48?
Yes, the EN_PMI_CORE* bits are set to 0xf.
>
> > When HT is on, only the 2 threads in one of the four cores receive the
> > interrupt.
> Something is not right here. Next week, I may be able to run some tests
> on a Nehalem using perfmon to compare. Could you also send me your
> latest uncore patch against tip-x86?
> Thanks.
I just send it out.
http://lkml.org/lkml/2010/12/2/4
Thanks,
Lin Ming
next prev parent reply other threads:[~2010-12-02 5:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 12:01 [RFC PATCH 2/3 v2] perf: Implement Nehalem uncore pmu Lin Ming
2010-11-21 12:46 ` Andi Kleen
2010-11-21 14:04 ` Lin Ming
2010-11-21 17:00 ` Andi Kleen
2010-11-21 17:44 ` Peter Zijlstra
2010-11-23 10:00 ` Stephane Eranian
2010-11-25 0:24 ` Lin Ming
2010-11-25 6:09 ` Peter Zijlstra
2010-11-25 6:27 ` Lin Ming
2010-11-25 8:48 ` Stephane Eranian
2010-11-25 18:20 ` Andi Kleen
2010-11-25 21:10 ` Stephane Eranian
2010-11-24 9:55 ` Lin Ming
2010-11-23 10:17 ` Stephane Eranian
2010-11-24 1:33 ` Lin Ming
2010-11-26 5:15 ` Lin Ming
2010-11-26 8:18 ` Stephane Eranian
2010-11-26 8:29 ` Lin Ming
2010-11-26 8:33 ` Stephane Eranian
2010-11-26 9:00 ` Lin Ming
2010-11-26 10:06 ` Stephane Eranian
2010-12-01 3:21 ` Lin Ming
2010-12-01 13:04 ` Stephane Eranian
2010-12-02 5:26 ` Lin Ming [this message]
2010-11-26 11:24 ` Peter Zijlstra
2010-11-26 11:25 ` Stephane Eranian
2010-11-26 11:36 ` Peter Zijlstra
2010-11-26 11:41 ` Stephane Eranian
2010-11-26 16:25 ` Lin Ming
2010-12-01 3:28 ` Lin Ming
2010-12-01 11:37 ` Peter Zijlstra
2010-12-01 14:08 ` Andi Kleen
2010-12-01 14:18 ` Peter Zijlstra
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=1291267599.2405.318.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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