Re: [PATCH RFC tip/core/rcu 0/30] RCU commits queued for 2.6.36/7

[Josh Triplett]

On Wed, Jul 14, 2010 at 01:09:45PM -0700, Paul E. McKenney wrote:
> This patchset shows the patches queued for 2.6.36/7.  These are not
> yet ready to move upstream due to dependencies on commits moving up other
> trees.  The patches are as follows:
> 
> 1-19.	These are the remaining patches implementing Arnd's sparse-checking
> 	work.  #1 needs to go up the networking tree, but
> 	will cause regressions until f5155b33277 ("rcu: add an
> 	rcu_dereference_index_check()") reaches mainline.  #2 depends
> 	on #1, and many of the later patches (#3-#30) depend on #2.
> 	Many of #3-#19 will go up non-tip trees.
> 20.	Update Documentation/RCU to remove the now-deprecated rcu_head
> 	initialization macros.
> 21.	Fix long-standing DocBook example showing long-dead three-argument
> 	variant of call_rcu().
> 22.	Make the CPU stall warning timeout configurable at build time
> 	with new RCU_CPU_STALL_TIMEOUT config parameter.
> 23.	Remove the now-deprecated rcu_head initialization macros.
> 	This depends on a couple of patches removing their use that
> 	are making their way up other maintainer trees.
> 24.	Document the new debug assists from Arnd, Mathieu, and myself.
> 25.	Add random preemption to rcutorture testing of preemptible
> 	RCU, courtesy of Lai Jiangshan.
> 26.	Remove TREE_RCU's ->rda[] array in favor of the new __percpu
> 	facility, also courtesy of Lai Jiangshan.
> 27.	Fixlet to #26 for RCU tracing.
> 28.	Rename __do_rcu_dereference_check() to rcu_lockdep_assert(),
> 	given that Tetsuo Handa has found outside-of-RCU use for this
> 	function.
> 29.	Add a boot parameter to suppress RCU CPU stall warnings.
> 30.	Update kerneldoc or rcu_read_lock(), call_rcu(), and
> 	synchronize_rcu().

I replied to patches 27 and 29 with suggested changes.  For all the
rest:

Reviewed-by: Josh Triplett <josh@xxxxxxxxxxxxxxxx>

- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/