korg/linux
0
0
Fork 0
mirror of https://mirrors.bfsu.edu.cn/git/linux.git synced 2024-11-26 05:34:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

watchdog: Update Kconfig entries

Browse Source 
The soft and hard lockup thresholds have changed so the
corresponding Kconfig entries need to be updated accordingly.
Add a reference to  watchdog_thresh while at it.

Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
Signed-off-by: Don Zickus <dzickus@redhat.com>
Link: http://lkml.kernel.org/r/1328827342-6253-2-git-send-email-dzickus@redhat.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
Fernando Luis Vázquez Cao 2012-02-09 17:42:21 -05:00 committed by Ingo Molnar
parent 9919cba7ff
commit 5f32908943
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
lib/Kconfig.debug
View File

@ -166,18 +166,21 @@ config LOCKUP_DETECTOR
hard and soft lockups. hard and soft lockups.
Softlockups are bugs that cause the kernel to loop in kernel Softlockups are bugs that cause the kernel to loop in kernel
mode for more than 60 seconds, without giving other tasks a mode for more than 20 seconds, without giving other tasks a
chance to run. The current stack trace is displayed upon chance to run. The current stack trace is displayed upon
detection and the system will stay locked up. detection and the system will stay locked up.
Hardlockups are bugs that cause the CPU to loop in kernel mode Hardlockups are bugs that cause the CPU to loop in kernel mode
for more than 60 seconds, without letting other interrupts have a for more than 10 seconds, without letting other interrupts have a
chance to run. The current stack trace is displayed upon detection chance to run. The current stack trace is displayed upon detection
and the system will stay locked up. and the system will stay locked up.
The overhead should be minimal. A periodic hrtimer runs to The overhead should be minimal. A periodic hrtimer runs to
generate interrupts and kick the watchdog task every 10-12 seconds. generate interrupts and kick the watchdog task every 4 seconds.
An NMI is generated every 60 seconds or so to check for hardlockups. An NMI is generated every 10 seconds or so to check for hardlockups.
The frequency of hrtimer and NMI events and the soft and hard lockup
thresholds can be controlled through the sysctl watchdog_thresh.
config HARDLOCKUP_DETECTOR config HARDLOCKUP_DETECTOR
def_bool LOCKUP_DETECTOR && PERF_EVENTS && HAVE_PERF_EVENTS_NMI && \ def_bool LOCKUP_DETECTOR && PERF_EVENTS && HAVE_PERF_EVENTS_NMI && \
@ -189,7 +192,8 @@ config BOOTPARAM_HARDLOCKUP_PANIC
help help
Say Y here to enable the kernel to panic on "hard lockups", Say Y here to enable the kernel to panic on "hard lockups",
which are bugs that cause the kernel to loop in kernel which are bugs that cause the kernel to loop in kernel
mode with interrupts disabled for more than 60 seconds. mode with interrupts disabled for more than 10 seconds (configurable
using the watchdog_thresh sysctl).
Say N if unsure. Say N if unsure.
@ -206,8 +210,8 @@ config BOOTPARAM_SOFTLOCKUP_PANIC
help help
Say Y here to enable the kernel to panic on "soft lockups", Say Y here to enable the kernel to panic on "soft lockups",
which are bugs that cause the kernel to loop in kernel which are bugs that cause the kernel to loop in kernel
mode for more than 60 seconds, without giving other tasks a mode for more than 20 seconds (configurable using the watchdog_thresh
chance to run. sysctl), without giving other tasks a chance to run.
The panic can be used in combination with panic_timeout, The panic can be used in combination with panic_timeout,
to cause the system to reboot automatically after a to cause the system to reboot automatically after a