From: Randy Dunlap <randy.dunlap@oracle.com>
To: Don Zickus <dzickus@redhat.com>
Cc: mingo@elte.hu, fweisbec@gmail.com, peterz@infradead.org,
gorcunov@gmail.com, aris@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] [watchdog] combine nmi_watchdog and softlockup
Date: Thu, 15 Apr 2010 15:32:51 -0700 [thread overview]
Message-ID: <20100415153251.590c91ca.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1271366710-17468-1-git-send-email-dzickus@redhat.com>
On Thu, 15 Apr 2010 17:25:10 -0400 Don Zickus wrote:
> arch/x86/kernel/apic/hw_nmi.c | 2 +-
> include/linux/sched.h | 6 +
> init/Kconfig | 1 +
> kernel/Makefile | 4 +-
> kernel/sysctl.c | 9 +
> kernel/watchdog.c | 570 +++++++++++++++++++++++++++++++++++++++++
> lib/Kconfig.debug | 21 +-
> 7 files changed, 605 insertions(+), 8 deletions(-)
> create mode 100644 kernel/watchdog.c
Updates to Documentation/kernel-parameters.txt ??
> +static int __init no_watchdog_setup(char *str)
> +{
> + no_watchdog = 1;
> + return 1;
> +}
> +__setup("no_watchdog", no_watchdog_setup);
New, please document.
> +/* deprecated */
> +static int __init nosoftlockup_setup(char *str)
> +{
> + no_watchdog = 1;
> + return 1;
> +}
That's not marked as deprecated anywhere?
> +__setup("nosoftlockup", nosoftlockup_setup);
> +static int __init nonmi_watchdog_setup(char *str)
> +{
> + no_watchdog = 1;
> + return 1;
> +}
> +__setup("nonmi_watchdog", nonmi_watchdog_setup);
New, please document.
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index e2e73cc..280794a 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -171,15 +171,24 @@ config DETECT_SOFTLOCKUP
> support it.)
>
> config NMI_WATCHDOG
> - bool "Detect Hard Lockups with an NMI Watchdog"
> - depends on DEBUG_KERNEL && PERF_EVENTS && PERF_EVENTS_NMI
> + bool "Detect Hard and Soft Lockups"
> + depends on DEBUG_KERNEL
> + default DETECT_SOFTLOCKUP
> help
> Say Y here to enable the kernel to use the NMI as a watchdog
> - to detect hard lockups. This is useful when a cpu hangs for no
preferably: CPU
> - reason but can still respond to NMIs. A backtrace is displayed
> - for reviewing and reporting.
> + to detect hard and soft lockups.
> +
> + Softlockups are bugs that cause the kernel to loop in kernel
> + mode for more than 60 seconds, without giving other tasks a
> + chance to run. The current stack trace is displayed upon
> + detection and the system will stay locked up.
> +
> + Hardlockups are bugs that cause the cpu to loop in kernel mode
ditto
> + for more than 60 seconds, without letting other interrupts a
have a
> + chance to run. The current stack trace is displayed upon detection
> + and the system will stay locked up.
>
> - The overhead should be minimal, just an extra NMI every few
> + The overhead should me minimal, just an extra NMI every few
be
> seconds.
>
> config BOOTPARAM_SOFTLOCKUP_PANIC
---
~Randy
next prev parent reply other threads:[~2010-04-15 22:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 21:25 Don Zickus
2010-04-15 22:32 ` Randy Dunlap [this message]
2010-04-16 14:12 ` Don Zickus
2010-04-16 1:47 ` Frederic Weisbecker
2010-04-16 14:12 ` Don Zickus
2010-04-16 14:43 ` Frederic Weisbecker
2010-04-16 15:04 ` Don Zickus
2010-04-16 15:32 ` Frederic Weisbecker
2010-04-16 16:14 ` Don Zickus
2010-04-16 16:24 ` Frederic Weisbecker
2010-04-16 14:32 ` Cyrill Gorcunov
2010-04-16 14:46 ` Frederic Weisbecker
2010-04-16 14:53 ` Peter Zijlstra
2010-04-16 14:59 ` Frederic Weisbecker
2010-04-16 14:54 ` Cyrill Gorcunov
2010-04-16 14:46 ` Don Zickus
2010-04-19 21:21 ` Don Zickus
2010-04-19 21:35 ` Ingo Molnar
2010-04-19 21:51 ` Don Zickus
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=20100415153251.590c91ca.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=aris@redhat.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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
Powered by JetHome