public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: 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: Wed, 24 Nov 2010 09:33:43 +0800	[thread overview]
Message-ID: <1290562423.2405.54.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <AANLkTikt8AkZjNahrzTStJ5qM0D4Z+H_7snZBgsABm24@mail.gmail.com>

On Tue, 2010-11-23 at 18:17 +0800, Stephane Eranian wrote:
> Lin,
> 
> On Sun, Nov 21, 2010 at 1:01 PM, Lin Ming <ming.m.lin@intel.com> wrote:
> > +static void uncore_pmu_enable_all(void)
> > +{
> > +       u64 ctrl;
> > +
> > +       /*
> > +        * (0xFULL << 48): 1 of the 4 cores can receive NMI each time
> > +        * but we don't know which core will receive the NMI when overflow happens
> > +        */
> 
> That does not sound right. If you set bit 48-51 to 1, then all 4 cores
> will receive EVERY
> interrupt, i.e., it's a broadcast. That seems to contradict your
> comment: 1 of the 4. Unless
> you meant, they all get the interrupt and one will handle it, the
> other will find nothing to
> process. But I don't see the atomic op that would make this true in
> uncore_handle_irq().

I thought it's a broadcast too in the v1 patches, let me double check
it.

> 
> I also think that if you want all processors to receive the
> interrupts, then the mask should
> be 0xff when HT is on. The manual is rather obscure on this, but it
> does make sense.

Kernel panics if 0xff is set, but it maybe bugs of my code.

Anyway, is it told in some errata that the mask should be 0xff when HT
is on?

Thanks,
Lin Ming

> 
> 
> > +       ctrl = ((1 << UNCORE_NUM_GENERAL_COUNTERS) - 1) | (0xFULL << 48);
> > +       ctrl |= MSR_UNCORE_PERF_GLOBAL_CTRL_EN_FC0;
> > +
> > +       /*
> > +        * Freeze the uncore pmu on overflow of any uncore counter.
> > +        * This makes unocre NMI handling easier.
> > +        */
> > +       ctrl |= MSR_UNCORE_PERF_GLOBAL_CTRL_PMI_FRZ;
> > +
> > +       wrmsrl(MSR_UNCORE_PERF_GLOBAL_CTRL, ctrl);
> > +}
> > +



  reply	other threads:[~2010-11-24  1:32 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 [this message]
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
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=1290562423.2405.54.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=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