From: Keith Owens <kaos@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NMI problems with Dell SMP Xeons
Date: Tue, 23 May 2006 12:21:56 +1000 [thread overview]
Message-ID: <6256.1148350916@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 23 May 2006 12:02:10 +1000." <5767.1148349730@kao2.melbourne.sgi.com>
Keith Owens (on Tue, 23 May 2006 12:02:10 +1000) wrote:
>Andi Kleen (on Tue, 23 May 2006 03:55:48 +0200) wrote:
>>nd add special cases just to get an NMI send with different vector.
>>>
>>> I have never disagreed that all NMIs will end up on the NMI vector (2).
>>
>>The problem was that KDB had an own handler for its debug vector,
>>although that was only ever called as NMI.
>
>You are confusing KDB_ENTER (instruction code 'int 0x81') with
>KDB_VECTOR (IPI). KDB_ENTER needs its own int handler which is not an
>NMI, KDB_VECTOR does not need (and does not have) its own handler, it
>is handled by the NMI vector.
Or you might be thinking of kdb-v0.6-2.2.13 and earlier, which did have
a spurious handler for KDB_VECTOR. But that was fixed in
kdb-v1.0-2.3.29, back in January 2000. You are not going to hold that
against me are you, especially since I was not maintaining KDB then?
next prev parent reply other threads:[~2006-05-23 2:23 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 [this message]
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=6256.1148350916@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=ak@suse.de \
--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