Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)
From: Maciej W. Rozycki (macro_at_linux-mips.org)
Date: 05/17/05
- Previous message: Richard B. Johnson: "Linux 2.6.11.9 aic7xxx SCSI errors"
- In reply to: Linus Torvalds: "Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)"
- Next in thread: Linus Torvalds: "Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)"
- Reply: Linus Torvalds: "Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 17 May 2005 18:04:05 +0100 (BST) To: Linus Torvalds <torvalds@osdl.org>
On Tue, 17 May 2005, Linus Torvalds wrote:
> > Mostly or perhaps even exclusively due to BIOS bugs -- you know, that
> > piece of hidden firmware that runs in the SMM under our feet and fiddles
> > randomly with hardware we can do nothing about.
>
> I'd love to just blame the BIOS, but we've definitely had our own share of
> bugs too. NMI makes all the fast system call etc stuff much more
> "exciting", and we've several times had code that does actually disable
> interrupts for a long time - which may be exceedingly impolite, but then
> the NMI watchdog makes it a fatal error rather than something that is just
> a nuisanse.
Well, this is actually not a problem with the watchdog itself. And I'd
rather say it's doing us a favour (and a great job) finding these buggy
bits of code that keep interrupts off CPUs. ;-)
Otherwise NMIs should be completely transparent. Well, yeah, that's
theory -- for this to be the case we'd have to use a task gate which is
rather time consuming and using an interrupt gate means we need to take
some explicit care elsewhere indeed.
OTOH, we can always get an NMI from the chipset in response e.g. to a bus
error of some kind (unfortunately it's often impossible to reroute these
errors to a more useful interrupt, like an MCE), so we need to be prepared
for one at any time. But these errors are expected to be rare, so it's
hard to test their effects, unlike these of the watchdog.
> Of course, our own bugs we can fix (and hopefully we have done so - many
> people _do_ obviously use the NMI watchdog as-is), so yes, in that sense
> BIOS (and hardware) bugs end up being a special case.
The problem with the SMM as currently used by BIOSes is unfortunately the
design, not any particular implementation.
Maciej
-
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/
- Previous message: Richard B. Johnson: "Linux 2.6.11.9 aic7xxx SCSI errors"
- In reply to: Linus Torvalds: "Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)"
- Next in thread: Linus Torvalds: "Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)"
- Reply: Linus Torvalds: "Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
