From: ebiederm@xmission.com (Eric W. Biederman)
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: Re: i386 nmi_watchdog: Merge check_nmi_watchdog fixes from x86_64
Date: Wed, 05 Oct 2005 14:00:48 -0600 [thread overview]
Message-ID: <m164sb7mz3.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <43442E8E.1090301@tmr.com> (Bill Davidsen's message of "Wed, 05 Oct 2005 15:50:38 -0400")
Bill Davidsen <davidsen@tmr.com> writes:
> Eric W. Biederman wrote:
>> The per cpu nmi watchdog timer is based on an event counter. idle cpus don't
>> generate events so the NMI watchdog doesn't fire
>> and the test to see if the watchdog is working fails.
>
> Question: given all the concern about reducing clocks and all, do we actually
> need nmi on more than one CPU? Are there cases where a single CPU hangs in idle
> on an SMP system?
I really don't know, but the normal interrupt rate is once per second or slower
if the cpu is idle. I was just working in the vicinity and discovered when
I enabled the nmi watchdog it failed to come on because it didn't handled it's
initialization test properly, and x86_64 had already fixed it.
Eric
next prev parent reply other threads:[~2005-10-05 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 15:02 Eric W. Biederman
2005-10-05 19:50 ` Bill Davidsen
2005-10-05 20:00 ` Eric W. Biederman [this message]
2005-10-12 1:26 ` Andrew Morton
2005-10-14 4:13 ` Eric W. Biederman
2005-10-14 18:53 ` Andy Isaacson
2005-10-15 12:49 ` Eric W. Biederman
2005-10-18 7:05 ` Andy Isaacson
2005-10-18 12:44 ` Eric W. Biederman
2005-10-19 7:10 ` 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=m164sb7mz3.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=davidsen@tmr.com \
--cc=fastboot@osdl.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
Powered by JetHome