[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080904201926.GN18288@one.firstfloor.org>
Date: Thu, 4 Sep 2008 22:19:26 +0200
From: Andi Kleen <andi@...stfloor.org>
To: "Mingarelli, Thomas" <Thomas.Mingarelli@...com>
Cc: Andi Kleen <andi@...stfloor.org>, Vivek Goyal <vgoyal@...hat.com>,
Don Zickus <dzickus@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Prarit Bhargava <prarit@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"arozansk@...hat.com" <arozansk@...hat.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Maciej W. Rozycki" <macro@...ux-mips.org>
Subject: Re: [PATCH RFC] NMI Re-introduce un[set]_nmi_callback
On Thu, Sep 04, 2008 at 08:01:31PM +0000, Mingarelli, Thomas wrote:
> Exactly.
>
> The hpwdt driver is meant to be a catch-all for any NMI coming through on ProLiant HW only. Moreover, for newer ProLiant HW at that.
>
> Once the NMI comes in, we call into our BIOS for the true reason of the NMI. That message gets logged to the IML in NVRAM for the user to view. We then panic the system.
The BIOS tells you about the NMI reason and tells you if the
watchdog didn't fire?
If yes that's great. You can be a good NMI citizen then.
Just check if the NMI came from your watchdog and if not return
NOTIFY_DONE
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists