Ok, I have reworked all the NMI code, moved it to it's own file, and
converted all the NMI users to use the NMI request/release code. The
current code will call call the NMI handlers on an NMI, interested
parties may detect that their NMI occurred and handle it. Since the NMI
into the CPU is edge-triggered, I think that's the correct way to handle
it (although it is slower). If someone figures out another way, that
would be very helpful. The include/linux/nmi.h and
arch/i386/kernel/nmi.c files were renamed to nmi_watchdog.h and
nmi_watchdog.c.
The biggest hole (that I know of) in these changes is that there is no
way that I can tell to detect if an nmi_watchdog has occurred if the NMI
source is the I/O APIC. That code will assume that if no one else has
handled the NMI, it was the source, which is a bad assumption (but the
same assumption that was being made before my changes, so it's no
worse). Most things should be using the local APIC, anyway.
It's now too big to include in an email, so it's at
http://home.attbi.com/~minyard/linux-nmi-v6.diff.
-Corey
-
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/
This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:26 EST