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 
In-reply-to: Your message of "Tue, 23 May 2006 12:02:10 +1000."
             <5767.1148349730@kao2.melbourne.sgi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 23 May 2006 12:21:56 +1000
Message-ID: <6256.1148350916@kao2.melbourne.sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1135
Lines: 24

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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/