From: Prarit Bhargava <prarit@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, arozansk@redhat.com,
dzickus@redhat.com, Thomas.Mingarelli@hp.com, ak@linux.intel.com,
mingo@elte.hu
Subject: Re: [PATCH RFC] NMI Re-introduce un[set]_nmi_callback
Date: Thu, 04 Sep 2008 10:29:20 -0400 [thread overview]
Message-ID: <48BFF0C0.7060208@redhat.com> (raw)
In-Reply-To: <1220535463.8609.223.camel@twins>
>
> Why is the DIE_NMIWATCHDOG notifier not sufficient for this driver?
>
>
Peter -- good question. The HP systems with this HW will use the hpwdt
driver in place of the default nmi watchdog. When the HW detects a
problem, the HW will generate a single NMI that the driver will handle.
The driver doesn't want the NMI to be rejected due to a reason code.
I'm sure that Thomas Mingarelli, who is cc'd, can provide further details.
From our quick conversation as well, you raised an interesting point
about oprofile, kgdb, and other subsystems that use the NMI notifier
chains -- they may be impacted by the NMI callback.
Don (dzickus) or Aris, do you have any thoughts on how to get around the
second issue? We could check to see if anything is registered on the
notifier chain and the fail to register the callback.
P.
next prev parent reply other threads:[~2008-09-04 14:36 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 [this message]
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
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=48BFF0C0.7060208@redhat.com \
--to=prarit@redhat.com \
--cc=Thomas.Mingarelli@hp.com \
--cc=ak@linux.intel.com \
--cc=arozansk@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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