lkml.org 
[lkml]   [2003]   [Jul]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
SubjectRe: [PATCH] NMI watchdog documentation
On Thu, Jul 31, 2003 at 12:53:00AM +0200, you [Mikael Pettersson] wrote:
> On Wed, 30 Jul 2003 22:40:52 +0300, Ville Herva wrote:
> >Ok, you got me confused (thankfully I didn't submit anything for inclusion
> >yet. :)
> ...
> >So... Should it be something like:
> >
> >+For x86-64, the needed APIC is always compiled in, and the NMI watchdog is
> >+always enabled with perctr mode. Currently, mode=2 (local APIC) does not
>
> always enabled with I/O-APIC mode.
>
> >+work on x86-64. IO APIC mode (mode=1) is the default. Using NMI watchdog
>
> Using local APIC
>
> >+(mode=1) needs the first performance register, so you can't use it for
>
> (mode=2)
>
> >+other purposes (such as high precision performance profiling.)
>
> >(Is the last sentence only valid for x86-64?)
>
> No, it's true for both x86 and x86-64. However, both oprofile
> and the perfctr driver disable the local APIC NMI watchdog, so
> the statement is only true for other drivers that don't do this.

Uuh, sorry. Is the one below ok by you for submission to Linus and Marcelo?


-- v --

v@iki.fi

--- linux/Documentation/nmi_watchdog.txt Sun Jul 27 19:58:26 2003
+++ linux~/Documentation/nmi_watchdog.txt Tue Jul 29 21:08:01 2003
@@ -1,9 +1,11 @@

-Is your ix86 system locking up unpredictably? No keyboard activity, just
+[NMI watchdog is available for x86 and x86-64 architectures]
+
+Is your system locking up unpredictably? No keyboard activity, just
a frustrating complete hard lockup? Do you want to help us debugging
such lockups? If all yes then this document is definitely for you.

-On Intel and similar ix86 type hardware there is a feature that enables
+On many x86/x86-64 type hardware there is a feature that enables
us to generate 'watchdog NMI interrupts'. (NMI: Non Maskable Interrupt
which get executed even if the system is otherwise locked up hard).
This can be used to debug hard kernel lockups. By executing periodic
@@ -20,6 +22,15 @@
kernel debugging options, such as Kernel Stack Meter or Kernel Tracer,
may implicitly disable the NMI watchdog.]

+For x86-64, the needed APIC is always compiled in, and the NMI watchdog is
+always enabled with I/O-APIC mode (nmi_watchdog=1). Currently, local APIC
+mode (nmi_watchdog=2) does not work on x86-64.
+
+Using local APIC (nmi_watchdog=2) needs the first performance register, so
+you can't use it for other purposes (such as high precision performance
+profiling.) However, at least oprofile and the perfctr driver disable the
+local APIC NMI watchdog automatically.
+
To actually enable the NMI watchdog, use the 'nmi_watchdog=N' boot
parameter. Eg. the relevant lilo.conf entry:

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
\
 
 \ /
  Last update: 2005-03-22 13:47    [W:0.049 / U:10.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site