lkml.org 
[lkml]   [2008]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH RFC] NMI Re-introduce un[set]_nmi_callback

>
> 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.


\
 
 \ /
  Last update: 2008-09-04 16:39    [W:0.083 / U:0.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site