From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
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 21:12:24 +0200 [thread overview]
Message-ID: <200305242111.07048.m.c.p@wolk-project.de> (raw)
In-Reply-To: <3ECFC2D6.2020007@gmx.net>
On Saturday 24 May 2003 21:07, Carl-Daniel Hailfinger wrote:
Hi Carl-Daniel,
> Documentation/nmi_watchdog.txt does not say which CONFIG_XYZ option has
> to be enabled to use the NMI watchdog, but it mentions that IO-APIC is
> somewhat related.
>
> Documentation/Configure.help is equally unclear. The NMI watchdog is
> mentioned as related to CONFIG_SMP, and the help text for
> CONFIG_X86_UP_APIC says: "The local APIC supports [..] the NMI watchdog"
> That does not necessarily mean that NMI is compiled in once local APIC
> support is selected.
>
> Can someone please shed some light on this issue? I'm willing to create
> a patch to fix the docs once I know if the NMI watchdog is compiled in
> alsways or on what it depends.
the nmi_watchdog is always compiled in if you select "CONFIG_X86_LOCAL_APIC"
see "arch/i386/kernel/Makefile"
ciao, Marc
next prev parent reply other threads:[~2003-05-24 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 19:07 Carl-Daniel Hailfinger
2003-05-24 19:08 ` Zwane Mwaikambo
2003-05-24 19:11 ` Zwane Mwaikambo
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 [this message]
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=200305242111.07048.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--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
all inboxes | Powered by JetHome®