From: John Levon <levon@movementarian.org>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: Corey Minyard <cminyard@mvista.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: NMI handling rework
Date: Thu, 7 Nov 2002 17:05:46 +0000 [thread overview]
Message-ID: <20021107170545.GA5914@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211070103540.27141-100000@montezuma.mastecende.com>
On Thu, Nov 07, 2002 at 01:20:20AM -0500, Zwane Mwaikambo wrote:
> How? The NMI interrupt should be internally masked till IRET. I think your
The question is not re-entrancy of the NMI handler (this cannot happen
indeed) but whether if when an NMI is generated, and the CPU is handling
an NMI, it will create another interrupt following the current one.
For the performance counters this seems to be the case, but Corey is
unsure about other sources of NMIs...
> you can therefore add tasks in with specific time intervals which will get
> triggered. This code currently is only running the nmi watchdog, but i'll
> be experimenting with various other handlers. I'll post a URL soon.
This can easily be built on top of the above API anyway, I think
regards
john
--
"When a man has nothing to say, the worst thing he can do is to say it
memorably."
- Calvin Trillin
next prev parent reply other threads:[~2002-11-07 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 6:44 Corey Minyard
2002-11-07 6:20 ` Zwane Mwaikambo
2002-11-07 16:51 ` Corey Minyard
2002-11-07 15:59 ` Maciej W. Rozycki
2002-11-07 16:38 ` Zwane Mwaikambo
2002-11-07 16:59 ` Richard B. Johnson
2002-11-07 19:58 ` Corey Minyard
2002-11-08 15:34 ` Alan Cox
2002-11-07 17:05 ` John Levon [this message]
2002-11-08 15:00 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-11-08 20:30 ` Zwane Mwaikambo
2002-11-11 15:26 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-11-15 3:45 ` Corey Minyard
2002-11-15 4:12 ` Zwane Mwaikambo
2002-11-15 4:50 ` Corey Minyard
2002-11-15 5:12 ` Zwane Mwaikambo
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=20021107170545.GA5914@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=zwane@holomorphy.com \
/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
Powered by JetHome