From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"" <linux-smp@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC] Fix NMI watchdog documentation
Date: Sat, 24 May 2003 15:11:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.50.0305241509380.2267-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0305241505470.2267-100000@montezuma.mastecende.com>
On Sat, 24 May 2003, Zwane Mwaikambo wrote:
> For nmi_watchdog=1 the NMI watchdog uses the programmable interval timer
> to trigger interrupt events via the IOAPIC. with nmi_watchdog=2 we use the
> performance counters on the processor to trigger these events. IOAPICs
> are generally found on SMP motherboards (but there are UP boards with
> them, it's chipset dependent). Generally i686+ (save some Athlons and a
> few other processors) will work with nmi_watchdog=2.
Forgot this bit;
w/ CONFIG_X86_LOCAL_APIC=y you only have nmi_watchdog=2
w/ CONFIG_X86_IO_APIC=y you have nmi_watchdog=1 and 2
w/ CONFIG_SMP you have nmi_watchdog=1 and 2 as it depends on
CONFIG_X86_IO_APIC
Zwane
--
function.linuxpower.ca
next prev parent reply other threads:[~2003-05-24 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 19:07 [RFC] Fix NMI watchdog documentation Carl-Daniel Hailfinger
2003-05-24 19:08 ` Zwane Mwaikambo
2003-05-24 19:11 ` Zwane Mwaikambo [this message]
2003-05-24 19:43 ` Carl-Daniel Hailfinger
2003-05-25 3:29 ` Valdis.Kletnieks
2003-05-25 3:36 ` Zwane Mwaikambo
2003-05-25 4:48 ` Valdis.Kletnieks
2003-05-25 5:03 ` Zwane Mwaikambo
2003-05-25 5:52 ` Disconnect
2003-05-24 19:12 ` Marc-Christian Petersen
2003-05-25 10:49 mikpe
2003-05-25 10:50 mikpe
2003-05-26 2:36 ` Valdis.Kletnieks
2003-05-26 5:31 ` Disconnect
2003-05-26 9:21 mikpe
2003-05-27 3:19 ` Valdis.Kletnieks
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=Pine.LNX.4.50.0305241509380.2267-100000@montezuma.mastecende.com \
--to=zwane@linuxpower.ca \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=mingo@redhat.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;
as well as URLs for NNTP newsgroup(s).