From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Clark Williams <clark.williams@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: unify boost and kthread priorities
Date: Wed, 17 Sep 2014 11:25:40 -0700 [thread overview]
Message-ID: <20140917182540.GG4723@linux.vnet.ibm.com> (raw)
In-Reply-To: <1410975957.31130.93.camel@x220>
On Wed, Sep 17, 2014 at 07:45:57PM +0200, Paul Bolle wrote:
> On Wed, 2014-09-17 at 10:17 -0700, Paul E. McKenney wrote:
> > On Wed, Sep 17, 2014 at 06:49:03PM +0200, Paul Bolle wrote:
> > > There's a reference to CONFIG_RCU_BOOST_PRIO in
> > > tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt. It needs
> > > updating too, doesn't it?
> >
> > Good catch!
> >
> > Also the one in tools/testing/selftests/rcutorture/configs/rcu/TREE03.
>
> >From my local perl monstrosity:
> # ... and Paul McKenney's rcutorture stuff (v3.14-rc+)
> if ($blob->[1] =~ /tools\/testing\/selftests\/rcutorture\/configs\/.*/) {
>
> Ie, I've made that script ignore all references to Kconfig macros below
> tools/testing/selftest/rcutorture/configs. Is that too crude?
It would not hurt to check the files that appear in the CFLIST files:
tools/testing/selftests/rcutorture/configs/lock/CFLIST
tools/testing/selftests/rcutorture/configs/rcu/CFLIST
These files drive the torture-test kernel configurations.
That said, yes, there are sometimes some obsolete or deprecated
Kconfig parameters in these files because some systems need them.
Thanx, Paul
> > Fixed both, thank you!
>
>
> Paul Bolle
>
prev parent reply other threads:[~2014-09-17 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 15:05 [PATCH] rcu: unify boost and kthread priorities Clark Williams
2014-09-16 20:41 ` Paul E. McKenney
2014-09-17 13:14 ` Clark Williams
2014-09-17 15:09 ` Paul E. McKenney
2014-09-17 16:49 ` Paul Bolle
2014-09-17 17:17 ` Paul E. McKenney
2014-09-17 17:45 ` Paul Bolle
2014-09-17 18:25 ` 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=20140917182540.GG4723@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=clark.williams@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.