From: george anzinger <george@mvista.com>
To: Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: NMI watchdog question.
Date: Tue, 05 Nov 2002 21:50:02 -0800 [thread overview]
Message-ID: <3DC8AD8A.20494DC0@mvista.com> (raw)
In io_apic.c there is the following bit of code:
if (nmi_watchdog) {
printk(KERN_WARNING "timer doesn't work through the
IO-APIC - disabling NMI Watchdog!\n");
nmi_watchdog = 0;
}
On at least some systems, disabling the above store leaves a
valid nmi watchdog timer.
In attempting to understand how the NMI watchdog works I
think I have found that:
a. the NMI interrupts are generated by the performance
counter in the cpu and
b. the test to see if the cpu is stalled is on a counter
that is bumped by the apic counter interrupt code.
If this is so (and help me to understand if it is not), then
what do the timer interrupts going thru the IO_APIC have to
do with the NMI watchdog.
Is it possible that the above code is a hold over from when
things were done differently?
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next reply other threads:[~2002-11-06 5:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 5:50 george anzinger [this message]
2002-11-06 10:53 ` NMI watchdog question Mikael Pettersson
2002-11-06 17:59 ` george anzinger
2002-11-06 18:12 ` John Levon
2002-11-06 18:58 ` Maciej W. Rozycki
2002-11-06 18:55 ` Maciej W. Rozycki
2002-11-06 19:49 ` george anzinger
2002-11-06 20:07 ` John Levon
2002-11-07 16:20 ` Bill Davidsen
2002-11-07 16:30 ` Maciej W. Rozycki
2002-11-07 16:44 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 0:53 Pallai Roland
[not found] <3EShS-A1-9@gated-at.bofh.it>
2005-03-06 15:14 ` Robert Hancock
2005-03-06 18:51 Pallai Roland
2005-03-07 10:16 Mikael Pettersson
2005-03-07 13:00 ` Pallai Roland
2005-03-08 2:28 Pallai Roland
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=3DC8AD8A.20494DC0@mvista.com \
--to=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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