From: Anton Blanchard <anton@samba.org>
To: fweisbec@gmail.com, mingo@elte.hu, a.p.zijlstra@chello.nl
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] lockup detector: CONFIG_DETECT_SOFTLOCKUP no longer exists
Date: Tue, 5 Jul 2011 13:32:40 +1000 [thread overview]
Message-ID: <20110705133240.25e81a7a@kryten> (raw)
Replace CONFIG_DETECT_SOFTLOCKUP with CONFIG_LOCKUP_DETECTOR.
Signed-off-by: Anton Blanchard <anton@samba.org>
---
Index: linux-2.6-work/lib/Kconfig.debug
===================================================================
--- linux-2.6-work.orig/lib/Kconfig.debug 2011-07-05 12:47:23.728166985 +1000
+++ linux-2.6-work/lib/Kconfig.debug 2011-07-05 12:47:40.478462898 +1000
@@ -227,7 +227,7 @@ config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE
config DETECT_HUNG_TASK
bool "Detect Hung Tasks"
depends on DEBUG_KERNEL
- default DETECT_SOFTLOCKUP
+ default LOCKUP_DETECTOR
help
Say Y here to enable the kernel to detect "hung tasks",
which are bugs that cause the task to be stuck in
@@ -866,7 +866,7 @@ config BOOT_PRINTK_DELAY
system, and then set "lpj=M" before setting "boot_delay=N".
NOTE: Using this option may adversely affect SMP systems.
I.e., processors other than the first one may not boot up.
- BOOT_PRINTK_DELAY also may cause DETECT_SOFTLOCKUP to detect
+ BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect
what it believes to be lockup conditions.
config RCU_TORTURE_TEST
next reply other threads:[~2011-07-05 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 3:32 Anton Blanchard [this message]
2011-07-05 10:34 ` [PATCH] lockup detector: CONFIG_DETECT_SOFTLOCKUP no longer exists Américo Wang
2011-07-05 12:56 ` [tip:core/locking] lockup detector: Fix reference to the non-existent CONFIG_DETECT_SOFTLOCKUP option tip-bot for Anton Blanchard
2011-07-05 13:51 ` [PATCH] lockup detector: CONFIG_DETECT_SOFTLOCKUP no longer exists Frederic Weisbecker
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=20110705133240.25e81a7a@kryten \
--to=anton@samba.org \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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