From: Don Zickus <dzickus@redhat.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: akpm@linux-foundation.org, a.p.zijlstra@chello.nl,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adjust hard-lockup related Kconfig options
Date: Mon, 10 Sep 2012 09:32:51 -0400 [thread overview]
Message-ID: <20120910133251.GK2151@redhat.com> (raw)
In-Reply-To: <504DF0FF020000780009A28E@nat28.tlf.novell.com>
On Mon, Sep 10, 2012 at 12:54:07PM +0100, Jan Beulich wrote:
> The main option should not appear in the resulting .config when the
> dependencies aren't met (i.e. use "depends on" rather than directly
> setting the default from the combined dependency values).
>
> The sub-options should depend on the main option rather than a more
> generic higher level one.
Looks good to me.
Acked-by: Don Zickus <dzickus@redhat.com>
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Cc: Don Zickus <dzickus@redhat.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> ---
> lib/Kconfig.debug | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> --- 3.6-rc5/lib/Kconfig.debug
> +++ 3.6-rc5-kconfig-cleanup-hardlockup/lib/Kconfig.debug
> @@ -196,12 +196,13 @@ config LOCKUP_DETECTOR
> thresholds can be controlled through the sysctl watchdog_thresh.
>
> config HARDLOCKUP_DETECTOR
> - def_bool LOCKUP_DETECTOR && PERF_EVENTS && HAVE_PERF_EVENTS_NMI && \
> - !HAVE_NMI_WATCHDOG
> + def_bool y
> + depends on LOCKUP_DETECTOR && !HAVE_NMI_WATCHDOG
> + depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI
>
> config BOOTPARAM_HARDLOCKUP_PANIC
> bool "Panic (Reboot) On Hard Lockups"
> - depends on LOCKUP_DETECTOR
> + depends on HARDLOCKUP_DETECTOR
> help
> Say Y here to enable the kernel to panic on "hard lockups",
> which are bugs that cause the kernel to loop in kernel
> @@ -212,7 +213,7 @@ config BOOTPARAM_HARDLOCKUP_PANIC
>
> config BOOTPARAM_HARDLOCKUP_PANIC_VALUE
> int
> - depends on LOCKUP_DETECTOR
> + depends on HARDLOCKUP_DETECTOR
> range 0 1
> default 0 if !BOOTPARAM_HARDLOCKUP_PANIC
> default 1 if BOOTPARAM_HARDLOCKUP_PANIC
>
>
>
prev parent reply other threads:[~2012-09-10 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 11:54 [PATCH] adjust hard-lockup related Kconfig options Jan Beulich
2012-09-10 13:32 ` Don Zickus [this message]
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=20120910133251.GK2151@redhat.com \
--to=dzickus@redhat.com \
--cc=JBeulich@suse.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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