From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
paul.mckenney@linaro.org, mmarek@suse.cz,
linux-kbuild@vger.kernel.org
Subject: Re: rcu: Provide compile-time control for no-CBs CPUs
Date: Tue, 30 Apr 2013 14:49:19 -0700 [thread overview]
Message-ID: <20130430214919.GL3780@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130430213831.GA3232@free.fr>
On Tue, Apr 30, 2013 at 11:38:31PM +0200, Yann E. MORIN wrote:
> Paul, Dave, All,
>
> On Tue, Apr 30, 2013 at 12:25:41PM -0700, Paul E. McKenney wrote:
> > On Tue, Apr 30, 2013 at 02:46:12PM -0400, Dave Jones wrote:
> > > On Tue, Apr 30, 2013 at 03:21:26PM +0000, Linux Kernel wrote:
> > >
> > > > +choice
> > > > + prompt "Build-forced no-CBs CPUs"
> > > > + default RCU_NOCB_CPU_NONE
> > > > + help
> > > > + This option allows no-CBs CPUs to be specified at build time.
> > > > + Additional no-CBs CPUs may be specified by the rcu_nocbs=
> > > > + boot parameter.
> > > > +
> > > > +config RCU_NOCB_CPU_NONE
> > > > + bool "No build_forced no-CBs CPUs"
> > > > + depends on RCU_NOCB_CPU
> > > > + help
> > > > + This option does not force any of the CPUs to be no-CBs CPUs.
> > > > + Only CPUs designated by the rcu_nocbs= boot parameter will be
> > > > + no-CBs CPUs.
> > > > +
> > > > +config RCU_NOCB_CPU_ZERO
> > > > + bool "CPU 0 is a build_forced no-CBs CPU"
> > > > + depends on RCU_NOCB_CPU
> > > > + help
> > > > + This option forces CPU 0 to be a no-CBs CPU. Additional CPUs
> > > > + may be designated as no-CBs CPUs using the rcu_nocbs= boot
> > > > + parameter will be no-CBs CPUs.
> > > > +
> > > > + Select this if CPU 0 needs to be a no-CBs CPU for real-time
> > > > + or energy-efficiency reasons.
> > > > +
> > > > +config RCU_NOCB_CPU_ALL
> > > > + bool "All CPUs are build_forced no-CBs CPUs"
> > > > + depends on RCU_NOCB_CPU
> > > > + help
> > > > + This option forces all CPUs to be no-CBs CPUs. The rcu_nocbs=
> > > > + boot parameter will be ignored.
> > > > +
> > > > + Select this if all CPUs need to be no-CBs CPUs for real-time
> > > > + or energy-efficiency reasons.
> > >
> > > Note that entering '?' when prompted in oldconfig only outputs the help
> > > parameter from the choice section.
> >
> > I must defer to the Kconfig experts on this issue. I have added them on CC.
>
> Yes. plain '?' will give you the help of the 'choice' menu itself.
>
> You can get the help entry for each option independently, by entering
> the index followed by a '?', eg. (built-up with copy-paste from above,
> actual display may vary slightly):
>
> Build-forced no-CBs CPUs
> > 1. No build_forced no-CBs CPUs (RCU_NOCB_CPU_NONE) (NEW)
> 2. CPU 0 is a build_forced no-CBs CPU (RCU_NOCB_CPU_ZERO) (NEW)
> 3. All CPUs are build_forced no-CBs CPUs (RCU_NOCB_CPU_ALL) (NEW)
> choice[1-3?]: 1?
>
> RCU_NOCB_CPU_NONE:
>
> This option does not force any of the CPUs to be no-CBs CPUs.
> Only CPUs designated by the rcu_nocbs= boot parameter will be
> no-CBs CPUs.
>
> Symbol: RCU_NOCB_CPU_NONE (=y)
> Type : boolean
> Prompt: No build_forced no-CBs CPUs
> Defined at: file:X
> Depends on: <choice>
> Location:
> -> blabla -> Build-forced no-CBs CPUs (<choice> (=y>)
Thank you for the info, Yann!
Thanx, Paul
prev parent reply other threads:[~2013-04-30 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130430152126.0C564660906@gitolite.kernel.org>
[not found] ` <20130430184612.GA14568@redhat.com>
2013-04-30 19:25 ` rcu: Provide compile-time control for no-CBs CPUs Paul E. McKenney
2013-04-30 20:24 ` Dave Jones
2013-04-30 21:48 ` Paul E. McKenney
2013-04-30 22:06 ` Dave Jones
2013-04-30 22:19 ` Paul E. McKenney
2013-04-30 21:38 ` Yann E. MORIN
2013-04-30 21:49 ` Paul E. McKenney [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=20130430214919.GL3780@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davej@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=paul.mckenney@linaro.org \
--cc=yann.morin.1998@free.fr \
/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