From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Ben Herrenschmidt <benh@kernel.crashing.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Hugh Dickins <hugh.dickins@tiscali.co.uk>
Subject: Re: CONFIG_PREEMPT_RCU in next/mmotm
Date: Wed, 12 Aug 2009 11:22:50 +0200 [thread overview]
Message-ID: <20090812092250.GD21655@elte.hu> (raw)
In-Reply-To: <20090812013422.GA23187@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Should these tests pass...
>
> Unless someone tells me otherwise, I will make a patch series
> intended to replace tip/core/rcu commits 7fe616c5d ("Simplify RCU
> CPU-hotplug notification"), 04b06256c ("Fix RCU & CPU hotplug
> hang"), and 7256cf0e83b ("Add diagnostic check for a possible
> CPU-hotplug race"), re-run all tests on that patchset, and submit
> the series. I expect the resulting patch set to have three
> patches, one to split out boot-time initialization for RCU_TREE, a
> second to create the cpu_notifier() API, and the third to make RCU
> use it.
Sure - we can reasonably rebase portions of that stack of commits:
earth4:~/tip> gll linus..core/rcu
7256cf0: rcu: Add diagnostic check for a possible CPU-hotplug race
04b0625: rcu: Fix RCU & CPU hotplug hang
7fe616c: rcu: Simplify RCU CPU-hotplug notification
240ebbf: rcu: Add synchronize_sched_expedited() rcutorture doc + updates
0acc512: rcu: Add synchronize_sched_expedited() torture tests
03b042b: rcu: Add synchronize_sched_expedited() primitive
c17ef45: rcu: Remove Classic RCU
Please mention the magic words "please reset core/rcu to 240ebbf
before applying these patches" in the mail to me, should i forget in
the days to come.
(hm, what was i supposed to not forget? Weird.)
Ingo
next prev parent reply other threads:[~2009-08-12 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 19:34 CONFIG_PREEMPT_RCU in next/mmotm Hugh Dickins
2009-08-08 23:56 ` Paul E. McKenney
2009-08-09 3:32 ` Hugh Dickins
2009-08-09 5:33 ` Paul E. McKenney
2009-08-09 11:24 ` Hugh Dickins
2009-08-09 13:06 ` Hugh Dickins
2009-08-09 18:57 ` Paul E. McKenney
2009-08-09 20:53 ` Hugh Dickins
2009-08-09 21:16 ` Paul E. McKenney
2009-08-10 3:39 ` Paul E. McKenney
2009-08-10 22:43 ` Paul E. McKenney
2009-08-12 1:34 ` Paul E. McKenney
2009-08-12 9:22 ` Ingo Molnar [this message]
2009-08-13 0:51 ` Paul E. McKenney
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=20090812092250.GD21655@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).