Re: [PATCH tip/core/rcu 15/24] rcu: Directly drive RCU_USER_QS from Kconfig

On Thu, May 14, 2015 at 02:27:48AM +0200, Frederic Weisbecker wrote: > On Wed, May 13, 2015 at 10:45:05AM -0700, Paul E. McKenney wrote: > > On Wed, May 13, 2015 at 02:37:52AM +0200, Frederic Weisbecker wrote: > > > On Tue, May 12, 2015 at 03:30:45PM -0700, Paul E. McKenney wrote: > > > > From: "Pa

Re: [PATCH tip/core/rcu 15/24] rcu: Directly drive RCU_USER_QS from Kconfig

On Wed, May 13, 2015 at 10:45:05AM -0700, Paul E. McKenney wrote: > On Wed, May 13, 2015 at 02:37:52AM +0200, Frederic Weisbecker wrote: > > On Tue, May 12, 2015 at 03:30:45PM -0700, Paul E. McKenney wrote: > > > From: "Paul E. McKenney" > > > > > > Currently, Kconfig will ask the user whether RC

Re: [PATCH tip/core/rcu 15/24] rcu: Directly drive RCU_USER_QS from Kconfig

On Wed, May 13, 2015 at 02:37:52AM +0200, Frederic Weisbecker wrote: > On Tue, May 12, 2015 at 03:30:45PM -0700, Paul E. McKenney wrote: > > From: "Paul E. McKenney" > > > > Currently, Kconfig will ask the user whether RCU_USER_QS should be set. > > This is silly because Kconfig already has all t

Re: [PATCH tip/core/rcu 15/24] rcu: Directly drive RCU_USER_QS from Kconfig

On Tue, May 12, 2015 at 03:30:45PM -0700, Paul E. McKenney wrote: > From: "Paul E. McKenney" > > Currently, Kconfig will ask the user whether RCU_USER_QS should be set. > This is silly because Kconfig already has all the information that it > needs to set this parameter. This commit therefore di

[PATCH tip/core/rcu 15/24] rcu: Directly drive RCU_USER_QS from Kconfig

From: "Paul E. McKenney" Currently, Kconfig will ask the user whether RCU_USER_QS should be set. This is silly because Kconfig already has all the information that it needs to set this parameter. This commit therefore directly drives the value of RCU_USER_QS via NO_HZ_FULL's "select" statement.