linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: ak@suse.de, vherva@niksula.hut.fi
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NMI watchdog documentation
Date: Wed, 30 Jul 2003 21:20:33 +0200 (MEST)	[thread overview]
Message-ID: <200307301920.h6UJKXwC020610@harpo.it.uu.se> (raw)

On Tue, 29 Jul 2003 20:53:19 +0300, Ville Herva wrote:
>On Tue, Jul 29, 2003 at 06:06:30PM +0200, you [Andi Kleen] wrote:
>> > 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?
>> 
>> Right, 1 and 2 need to be exchanged. Anyways local apic mode does not seem
>> to work, the kernel always reportss "NMI stuck" at bootup.
>> IO APIC mode for is default.
...
>+For x86-64, the needed APIC is always compiled in, and the NMI watchdog is
>+always enabled with perfctr mode. Currently, mode=1 does not work on x86-64.

Didn't Andi just say it's the other way around? nmi_watchdog=1 (I/O-APIC)
by default since nmi_watchdog=2 (local APIC) doesn't work.

/Mikael

             reply	other threads:[~2003-07-30 19:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 19:20 Mikael Pettersson [this message]
2003-07-30 19:40 ` [PATCH] NMI watchdog documentation 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:18 Mikael Pettersson
2003-07-29 10:37 Mikael Pettersson
2003-07-29 16:06 ` Andi Kleen
2003-07-29 17:53   ` Ville Herva
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=200307301920.h6UJKXwC020610@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.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).