From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rcu: remove duplicate CONFIG_RCU_CPU_STALL_DETECTOR
Date: Wed, 21 Jan 2009 23:17:05 -0800 [thread overview]
Message-ID: <20090122071705.GC6290@linux.vnet.ibm.com> (raw)
In-Reply-To: <4977CFFE.2020405@cn.fujitsu.com>
On Thu, Jan 22, 2009 at 09:46:38AM +0800, Lai Jiangshan wrote:
>
> Impact: remove the old CONFIG_RCU_CPU_STALL_DETECTOR
>
> tree_rcu introduce CONFIG_RCU_CPU_STALL_DETECTOR again.
>
> These two are the same exactly except:
> the old one "depends on CLASSIC_RCU"
> the new one "depends on CLASSIC_RCU || TREE_RCU"
>
> This patch remove the old one.
Good eyes!
However, Jiri Kosina has already queued this up for the trivial tree:
http://lkml.org/lkml/2009/1/15/218
Thanx, Paul
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 4c9ae60..e770e85 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -633,19 +633,6 @@ config RCU_TORTURE_TEST_RUNNABLE
>
> config RCU_CPU_STALL_DETECTOR
> bool "Check for stalled CPUs delaying RCU grace periods"
> - depends on CLASSIC_RCU
> - default n
> - help
> - This option causes RCU to printk information on which
> - CPUs are delaying the current grace period, but only when
> - the grace period extends for excessive time periods.
> -
> - Say Y if you want RCU to perform such checks.
> -
> - Say N if you are unsure.
> -
> -config RCU_CPU_STALL_DETECTOR
> - bool "Check for stalled CPUs delaying RCU grace periods"
> depends on CLASSIC_RCU || TREE_RCU
> default n
> help
>
>
next prev parent reply other threads:[~2009-01-22 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 1:46 [PATCH] rcu: remove duplicate CONFIG_RCU_CPU_STALL_DETECTOR Lai Jiangshan
2009-01-22 7:17 ` Paul E. McKenney [this message]
2009-01-22 8:30 ` Ingo Molnar
2009-01-22 9:45 ` Paul E. McKenney
2009-01-22 9:48 ` Jiri Kosina
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=20090122071705.GC6290@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.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