public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: Brendan Trotter <btrotter@gmail.com>, Keith Owens <kaos@sgi.com>,
	Andi Kleen <ak@suse.de>, Ashok Raj <ashok.raj@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: NMI problems with Dell SMP Xeons
Date: Wed, 7 Jun 2006 17:41:35 -0700	[thread overview]
Message-ID: <20060607174135.A27195@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060607114747.A25548@unix-os.sc.intel.com>; from rajesh.shah@intel.com on Wed, Jun 07, 2006 at 11:47:47AM -0700

On Wed, Jun 07, 2006 at 11:47:47AM -0700, Rajesh Shah wrote:
> On Wed, Jun 07, 2006 at 03:18:57PM +0000, Brendan Trotter wrote:
> > 
> > > I will try forcing send_IPI_allbutself() to use the mask version rather
> > > than the broadcast shortcut.  Later tonight ...
> > 
> > I've been looking into this a little - it appears that Linux tries to
> > use one bit per CPU in the local APIC's "logical destination register"
> > and that in all cases at least one bit is set for each valid CPU. As
> > far as I can tell sending an NMI (or any other broadcast IPI) in
> > logical mode with no shorthand and "destination = 0xFF" should work
> > fine for both "cluster mode" and "flat mode". In this case I'd also
> > suggest that "clear_local_APIC()" clear the destination format
> > register (DFR) and the logical destination register (LDR) so that it
> > doesn't receive broadcast NMIs if the CPU is taken offline.
> > 
> I will double-check with the CPU folks, but I don't think this
> will do what you want it to do. If you send an NMI IPI with
> destination set to 0xff, I think it will interrupt all CPUs,

I was wrong - a (reasonably modern) CPU will indeed not take the
NMI IPI if its LDR is clear and the IPI was sent in logical mode.
However, the CPU folks weren't expecting it to be used this way,
so they aren't sure yet if this is guaranteed to work this way
on all CPUs. 

Rajesh

  reply	other threads:[~2006-06-08  0:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22  9:08 NMI problems with Dell SMP Xeons Keith Owens
2006-05-22 23:56 ` Andi Kleen
2006-05-23  1:26   ` Keith Owens
2006-05-23  1:55     ` Andi Kleen
2006-05-23  2:02       ` Keith Owens
2006-05-23  2:21         ` Keith Owens
2006-05-23  5:03 ` Keith Owens
2006-06-07  4:49   ` Keith Owens
2006-06-07  7:20     ` Andi Kleen
2006-06-07  7:43       ` Keith Owens
2006-06-07  8:01         ` Andi Kleen
2006-06-07 11:47           ` Keith Owens
2006-06-07 12:13             ` Andi Kleen
2006-06-07 15:18         ` Brendan Trotter
2006-06-07 15:23           ` Andi Kleen
2006-06-07 18:47           ` Rajesh Shah
2006-06-08  0:41             ` Rajesh Shah [this message]
2006-06-08  0:46           ` Rajesh Shah
2006-06-08  5:11           ` Keith Owens

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=20060607174135.A27195@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=ak@suse.de \
    --cc=ashok.raj@intel.com \
    --cc=btrotter@gmail.com \
    --cc=kaos@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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