public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yong Wang <yong.y.wang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: One question about perf_counter on IA
Date: Wed, 27 May 2009 16:46:35 +0200	[thread overview]
Message-ID: <20090527144635.GA7300@elte.hu> (raw)
In-Reply-To: <20090527071736.GA26774@ywang-moblin2.bj.intel.com>


* Yong Wang <yong.y.wang@linux.intel.com> wrote:

> I noticed that the LVT error register is masked and then unmasked 
> during perf_counter initialization on IA in 
> arch/x86/kernel/cpu/perf_counter.c
> 
> void perf_counters_lapic_init(int nmi)
> {
> 	u32 apic_val;
> 
> 	if (!x86_pmu_initialized())
> 		return;
> 
> 	/*
> 	 * Enable the performance counter vector in the APIC LVT:
> 	 */
> 	apic_val = apic_read(APIC_LVTERR);
> 
> 	apic_write(APIC_LVTERR, apic_val | APIC_LVT_MASKED);
> 	if (nmi)
> 		apic_write(APIC_LVTPC, APIC_DM_NMI);
> 	else
> 		apic_write(APIC_LVTPC, LOCAL_PERF_VECTOR);
> 	apic_write(APIC_LVTERR, apic_val);
> }
> 
> Why is this needed? Is this documented somewhere in the spec? I 
> tried commenting out the masking and unmasking operations and I 
> did not any error interrupt generated.

i think a spurious error irq can be triggered due to APIC_DM_NMI 
having zero for the vector bit. If we switch between irq and nmi 
mode frequently then there could be racy situations.

Not that having an error irq would hurt much ...

Note, in the current code we essentially always use NMI mode, the 
cleanups just have not propagated through fully yet. Feel free to 
send a patch for this!

	Ingo

      reply	other threads:[~2009-05-27 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  7:17 One question about perf_counter on IA Yong Wang
2009-05-27 14:46 ` Ingo Molnar [this message]

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=20090527144635.GA7300@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yong.y.wang@linux.intel.com \
    /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