From: Andi Kleen <andi@firstfloor.org>
To: "Mingarelli, Thomas" <Thomas.Mingarelli@hp.com>
Cc: Andi Kleen <andi@firstfloor.org>, Vivek Goyal <vgoyal@redhat.com>,
Don Zickus <dzickus@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Prarit Bhargava <prarit@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arozansk@redhat.com" <arozansk@redhat.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH RFC] NMI Re-introduce un[set]_nmi_callback
Date: Thu, 4 Sep 2008 22:19:26 +0200 [thread overview]
Message-ID: <20080904201926.GN18288@one.firstfloor.org> (raw)
In-Reply-To: <183C1D5A376DE343AA8F94FC2A1EC14938D3E74841@GVW1091EXB.americas.hpqcorp.net>
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
next prev parent reply other threads:[~2008-09-04 20:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 13:07 [PATCH RFC] NMI Re-introduce un[set]_nmi_callback Prarit Bhargava
2008-09-04 13:37 ` Peter Zijlstra
2008-09-04 14:29 ` Prarit Bhargava
2008-09-04 14:49 ` aris
2008-09-04 14:56 ` Ingo Molnar
2008-09-04 15:12 ` H. Peter Anvin
2008-09-04 15:18 ` Ingo Molnar
2008-09-04 15:52 ` Andi Kleen
2008-09-04 17:20 ` Don Zickus
2008-09-04 17:52 ` Andi Kleen
2008-09-04 18:26 ` Don Zickus
2008-09-04 18:47 ` Andi Kleen
2008-09-04 19:08 ` Vivek Goyal
2008-09-04 20:00 ` Andi Kleen
2008-09-04 20:01 ` Mingarelli, Thomas
2008-09-04 20:19 ` Andi Kleen [this message]
2008-09-04 20:21 ` Mingarelli, Thomas
2008-09-04 20:53 ` Andi Kleen
2008-09-04 21:22 ` Don Zickus
2008-09-04 20:57 ` Vivek Goyal
2008-09-04 21:05 ` Mingarelli, Thomas
2008-09-04 21:21 ` Vivek Goyal
2008-09-04 21:24 ` Don Zickus
2008-09-04 21:46 ` Vivek Goyal
2008-09-05 8:57 ` Ingo Molnar
2008-09-05 10:24 ` Ingo Molnar
2008-09-05 9:33 ` Ingo Molnar
2008-09-05 14:16 ` Vivek Goyal
2008-09-05 14:18 ` Andi Kleen
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=20080904201926.GN18288@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Thomas.Mingarelli@hp.com \
--cc=ak@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arozansk@redhat.com \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
/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