Re: [PATCH tip/core/rcu 14/24] rcu: Directly drive TASKS_RCU from Kconfig

2015-05-13 Thread Paul E. McKenney
On Wed, May 13, 2015 at 09:31:19AM -0400, Steven Rostedt wrote: > On Tue, 12 May 2015 15:30:44 -0700 > "Paul E. McKenney" wrote: > > > From: "Paul E. McKenney" > > > > Currently, Kconfig will ask the user whether TASKS_RCU should be set. > > This is silly because Kconfig already has all the inf

Re: [PATCH tip/core/rcu 14/24] rcu: Directly drive TASKS_RCU from Kconfig

2015-05-13 Thread Steven Rostedt
On Tue, 12 May 2015 15:30:44 -0700 "Paul E. McKenney" wrote: > From: "Paul E. McKenney" > > Currently, Kconfig will ask the user whether TASKS_RCU should be set. > This is silly because Kconfig already has all the information that it > needs to set this parameter. This commit therefore directl

[PATCH tip/core/rcu 14/24] rcu: Directly drive TASKS_RCU from Kconfig

2015-05-12 Thread Paul E. McKenney
From: "Paul E. McKenney" Currently, Kconfig will ask the user whether TASKS_RCU 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 TASKS_RCU via "select" statements. Which means tha