From: Corey Minyard <cminyard@mvista.com>
To: John Levon <levon@movementarian.org>
Cc: dipankar@gamebox.net, linux-kernel@vger.kernel.org
Subject: [PATCH] NMI request/release, version 6 - "Well I thought the last one was ready"
Date: Thu, 24 Oct 2002 20:22:33 -0500 [thread overview]
Message-ID: <3DB89CD9.5090409@mvista.com> (raw)
In-Reply-To: 20021024202910.GA16192@compsoc.man.ac.uk
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
next prev parent reply other threads:[~2002-10-25 1:16 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 1:32 [PATCH] NMI request/release Corey Minyard
2002-10-22 2:10 ` John Levon
2002-10-22 2:32 ` Corey Minyard
2002-10-22 2:53 ` John Levon
2002-10-22 13:02 ` Corey Minyard
2002-10-22 15:09 ` John Levon
2002-10-22 16:03 ` Corey Minyard
2002-10-22 17:23 ` Robert Love
2002-10-22 18:08 ` Corey Minyard
2002-10-22 18:16 ` Robert Love
2002-10-22 20:04 ` Dipankar Sarma
2002-10-22 17:53 ` Dipankar Sarma
2002-10-22 18:05 ` Corey Minyard
2002-10-22 18:08 ` Dipankar Sarma
2002-10-22 18:29 ` Corey Minyard
2002-10-22 19:08 ` John Levon
2002-10-22 21:36 ` [PATCH] NMI request/release, version 3 Corey Minyard
2002-10-23 17:33 ` Dipankar Sarma
2002-10-23 18:03 ` Corey Minyard
2002-10-23 18:57 ` Dipankar Sarma
2002-10-23 20:14 ` [PATCH] NMI request/release, version 4 Corey Minyard
2002-10-23 20:50 ` Dipankar Sarma
2002-10-23 21:53 ` Corey Minyard
2002-10-24 7:41 ` Dipankar Sarma
2002-10-24 13:08 ` Corey Minyard
2002-10-24 7:50 ` Dipankar Sarma
2002-10-24 13:05 ` Corey Minyard
2002-10-24 13:28 ` [PATCH] NMI request/release, version 5 - I think this one's ready Corey Minyard
2002-10-24 14:46 ` John Levon
2002-10-24 15:36 ` Corey Minyard
2002-10-24 17:18 ` John Levon
2002-10-24 17:43 ` Corey Minyard
2002-10-24 18:04 ` John Levon
2002-10-24 18:32 ` Corey Minyard
2002-10-24 18:47 ` John Levon
2002-10-24 20:03 ` Corey Minyard
2002-10-24 20:29 ` John Levon
2002-10-25 1:22 ` Corey Minyard [this message]
2002-10-25 1:39 ` [PATCH] NMI request/release, version 6 - "Well I thought the last one was ready" John Levon
2002-10-25 1:58 ` Jeff Garzik
2002-10-25 2:01 ` [PATCH] NMI request/release, version 7 - minor cleanups Corey Minyard
2002-10-25 13:26 ` [PATCH] NMI request/release, version 8 Corey Minyard
2002-10-22 12:23 ` [PATCH] NMI request/release Suparna Bhattacharya
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=3DB89CD9.5090409@mvista.com \
--to=cminyard@mvista.com \
--cc=dipankar@gamebox.net \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).