public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Keith Owens <kaos@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NMI problems with Dell SMP Xeons
Date: Tue, 23 May 2006 01:56:39 +0200	[thread overview]
Message-ID: <200605230156.40149.ak@suse.de> (raw)
In-Reply-To: <12475.1148288884@kao2.melbourne.sgi.com>


> (1) IPI 2, not marked as NMI.  This does _not_ call into the do_nmi()
>     routine.
> 
>     People have been telling me (hi, Andi:) that sending interrupt 2 as
>     an IPI automatically sends it as an NMI. 

I can't remember ever saying that. I said that sending anything with the 
NMI bit set will end up at the NMI vector, not the original vector
you specified. Or at least that is what the Intel manual specify.
That is why it is useless to hook the original vector like you did
and add special cases just to get an NMI send with different vector.

-Andi




  reply	other threads:[~2006-05-23  0:01 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 [this message]
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
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=200605230156.40149.ak@suse.de \
    --to=ak@suse.de \
    --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