From: Mikael Pettersson <mikpe@csd.uu.se>
To: ak@suse.de
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br,
torvalds@osdl.org, vherva@niksula.hut.fi
Subject: Re: [PATCH] NMI watchdog documentation
Date: Wed, 30 Jul 2003 21:18:54 +0200 (MEST) [thread overview]
Message-ID: <200307301918.h6UJIskn020572@harpo.it.uu.se> (raw)
On Tue, 29 Jul 2003 18:06:30 +0200, Andi Kleen wrote:
>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.
That's strange. I've tested perfctr-generated interrupts through
the local APIC on Opteron, and they work with the perfctr driver.
Two things you might want to test:
- In case the unofficial event 0x76 really doesn't work in your
version of the chip, try this event specifier instead: it
creates a clock-like event using an inverted threshold approach.
I've tested this on K8 and P6 with the perfctr driver. The event
code (0xC0) is immaterial, 0x00 and 0xFF work equally well.
--- linux-2.6.0-test2/arch/x86_64/kernel/nmi.c.~1~ 2003-07-03 12:32:44.000000000 +0200
+++ linux-2.6.0-test2/arch/x86_64/kernel/nmi.c 2003-07-30 20:46:21.412657728 +0200
@@ -51,7 +51,7 @@
#define K7_EVNTSEL_OS (1 << 17)
#define K7_EVNTSEL_USR (1 << 16)
#define K7_EVENT_CYCLES_PROCESSOR_IS_RUNNING 0x76
-#define K7_NMI_EVENT K7_EVENT_CYCLES_PROCESSOR_IS_RUNNING
+#define K7_NMI_EVENT (0xC0 | (1<<23) | (0xFF << 24))
#define P6_EVNTSEL0_ENABLE (1 << 22)
#define P6_EVNTSEL_INT (1 << 20)
- My perfctr driver routes interrupts through LVTPC programmed for
Fixed delivery mode. Maybe the NMI delivery mode is broken. You
could try changing the NMI watchdog to use a new vector and Fixed
delivery mode, just to see if the watchdog starts ticking.
/Mikael
next reply other threads:[~2003-07-30 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 19:18 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 21:25 [PATCH] NMI watchdog documentation 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-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=200307301918.h6UJIskn020572@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).