Re: CONFIG_PREEMPT_RCU in next/mmotm

[Ingo Molnar <mingo@elte.hu>]

* 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