public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Kaibin Li <kaibinlee@gmail.com>,
	trivial@kernel.org, Dipankar Sarma <dipankar@in.ibm.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] Remove a duplicated option of RCU_CPU_STALL_DETECTOR
Date: Tue, 13 Jan 2009 15:34:50 -0800	[thread overview]
Message-ID: <20090113233450.GD6756@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0901132346150.5377@jikos.suse.cz>

On Tue, Jan 13, 2009 at 11:48:44PM +0100, Jiri Kosina wrote:
> On Tue, 13 Jan 2009, Kaibin Li wrote:
> 
> > There is a duplicated option of "Check for stalled CPUs delaying RCU
> > grace periods" in Kernel hacking.

Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

> > Signed-off-by: Kaibin Li <kaibinlee@gmail.com>
> > ---
> >  lib/Kconfig.debug |   13 -------------
> >  1 files changed, 0 insertions(+), 13 deletions(-)
> > 
> > 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
> 
> The RCU_CPU_STALL_DETECTOR indeed is duplicate, but the entries themselves 
> are not identical, as they have different dependencies.
> 
> Paul -- does Kaibin's patch remove the correct one? If so, I can take it 
> through trivial tree.

Indeed it is:  http://lkml.org/lkml/2008/12/23/167  ;-)

CCing Ingo in case he has it queued up.

							Thanx, Paul

  reply	other threads:[~2009-01-13 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090113140636.1515e11f@zenwalk.fortinet.com>
2009-01-13 22:48 ` [PATCH] Remove a duplicated option of RCU_CPU_STALL_DETECTOR Jiri Kosina
2009-01-13 23:34   ` Paul E. McKenney [this message]
2009-01-15 12:28     ` 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=20090113233450.GD6756@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=jkosina@suse.cz \
    --cc=kaibinlee@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=trivial@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