From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Aristeu Rozanski <aris@redhat.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] nmi_watchdog: update procfs nmi_watchdog file documentation
Date: Thu, 30 Oct 2008 18:45:34 +0300 [thread overview]
Message-ID: <20081030154534.GA19888@localhost> (raw)
In-Reply-To: <20081030151712.GO771@redhat.com>
[Aristeu Rozanski - Thu, Oct 30, 2008 at 11:17:14AM -0400]
| This patch updates the /proc/sys/kernel/nmi_watchdog documentation.
|
| Signed-off-by: Aristeu Rozanski <aris@redhat.com>
|
| ---
| Documentation/filesystems/proc.txt | 13 ++++++++-----
| Documentation/nmi_watchdog.txt | 5 +++++
| 2 files changed, 13 insertions(+), 5 deletions(-)
|
| --- linus-2.6.orig/Documentation/nmi_watchdog.txt 2008-10-24 11:41:30.000000000 -0400
| +++ linus-2.6/Documentation/nmi_watchdog.txt 2008-10-29 16:38:12.000000000 -0400
| @@ -69,6 +69,11 @@ to the overall system performance.
| On x86 nmi_watchdog is disabled by default so you have to enable it with
| a boot time parameter.
|
| +It's possible to disable the NMI watchdog in run-time by writing "0" to
| +/proc/sys/kernel/nmi_watchdog. Writing "1" to the same file will re-enable
| +the NMI watchdog. Notice that you still need to use "nmi_watchdog=" parameter
| +in boot time.
| +
| NOTE: In kernels prior to 2.4.2-ac18 the NMI-oopser is enabled unconditionally
| on x86 SMP boxes.
|
| --- linus-2.6.orig/Documentation/filesystems/proc.txt 2008-10-24 11:41:28.000000000 -0400
| +++ linus-2.6/Documentation/filesystems/proc.txt 2008-10-30 11:16:36.000000000 -0400
| @@ -1336,12 +1336,15 @@ panic controls already in that directory
| nmi_watchdog
| ------------
|
| -Enables/Disables the NMI watchdog on x86 systems. When the value is non-zero
| +Enables/Disables the NMI watchdog on x86 systems. When the value is non-zero
| the NMI watchdog is enabled and will continuously test all online cpus to
| -determine whether or not they are still functioning properly.
| -
| -Because the NMI watchdog shares registers with oprofile, by disabling the NMI
| -watchdog, oprofile may have more registers to utilize.
| +determine whether or not they are still functioning properly. Currently,
| +passing "nmi_watchdog=" parameter in boot time is required for this function
| +to work.
| +
| +If LAPIC NMI watchdog method is in use (nmi_watchdog=2 kernel parameter), the
| +NMI watchdog shares registers with oprofile, by disabling the NMI watchdog,
| +oprofile may have more registers to utilize.
|
| msgmni
| ------
|
Hi Aristeu,
by reading this patch I found that maybe it's time to start
using nmi_watchdog=[lapic,ioapic] instead of 1 and 2? We could make
them as alases to existing numbers. Thoughts?
- Cyrill -
next prev parent reply other threads:[~2008-10-30 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 15:17 [PATCH] nmi_watchdog: update procfs nmi_watchdog file documentation Aristeu Rozanski
2008-10-30 15:45 ` Cyrill Gorcunov [this message]
2008-10-30 15:51 ` Aristeu Rozanski
2008-10-30 15:51 ` Cyrill Gorcunov
2008-10-30 16:19 ` Randy Dunlap
2008-10-30 17:08 ` [PATCH] nmi_watchdog: update procfs nmi_watchdog file documentation v2 Aristeu Rozanski
2008-10-30 17:13 ` Randy Dunlap
2008-10-30 18:07 ` Ingo Molnar
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=20081030154534.GA19888@localhost \
--to=gorcunov@gmail.com \
--cc=aris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.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