From: Mikael Pettersson <mikpe@csd.uu.se>
To: ak@suse.de, vherva@niksula.hut.fi
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br,
torvalds@osdl.org
Subject: Re: [PATCH] NMI watchdog documentation
Date: Tue, 29 Jul 2003 12:37:33 +0200 (MEST) [thread overview]
Message-ID: <200307291037.h6TAbX9G026932@harpo.it.uu.se> (raw)
On Mon, 28 Jul 2003 19:53:42 +0200, Andi Kleen wrote:
>On Wed, 23 Jul 2003 20:43:25 +0300
>Ville Herva <vherva@niksula.hut.fi> wrote:
>
>> Documentation/nmi-watchdoc.txt doesn't actually tell what options need to be
>> enabled in kernel config in order to use NMI watchdog. I for one found it
>> confusing.
>>
>> I vaguely recall someone posted a similar patch some time ago, but it still
>> doesn't seem to be present in 2.4 or 2.6-test.
>>
>> Andi: what about x86-64 - does it have something similar that should be
>> mentioned?
>
>x86-64 is the same, except APIC is always compiled in and the nmi watchdog is
>always enabled with perfctr mode. mode=2 seems to also not work correctly currently.
>
>However one caveat (even for i386): when you use perfctr mode 1 you lose the first
>performance register which you may need for other things.
Andi, you have the numbers mixed up. mode 1 is I/O-APIC, mode 2 is local APIC,
and x86-64 defaults nmi_watchdog to I/O-APIC mode.
Now, is it the I/O-APIC or local APIC watchdog that doesn't work in x86-64?
/Mikael
next reply other threads:[~2003-07-29 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 10:37 Mikael Pettersson [this message]
2003-07-29 16:06 ` [PATCH] NMI watchdog documentation Andi Kleen
2003-07-29 17:53 ` Ville Herva
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 21:25 Mikael Pettersson
2003-07-30 22:53 Mikael Pettersson
2003-07-31 5:44 ` Ville Herva
2003-07-30 19:20 Mikael Pettersson
2003-07-30 19:40 ` Ville Herva
2003-07-30 19:18 Mikael Pettersson
2003-07-23 17:43 Ville Herva
2003-07-28 17:53 ` Andi Kleen
2003-07-28 19:21 ` Ville Herva
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=200307291037.h6TAbX9G026932@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@osdl.org \
--cc=vherva@niksula.hut.fi \
/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).