rcu: Directly drive TASKS_RCU from Kconfig

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 that
as subsystems require TASKS_RCU, those subsystems will need to add
"select" statements of their own.

Reported-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Reviewed-by: Pranith Kumar <bobby.prani@gmail.com>

1 files changed, 1 insertions, 3 deletions

diff --git a/init/Kconfig b/init/Kconfig
index dc24dec60232..73db30a76afa 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -509,7 +509,7 @@ config SRCU
           sections.
 
 config TASKS_RCU
-        bool "Task_based RCU implementation using voluntary context switch"
+        bool
         default n
         select SRCU
         help
@@ -517,8 +517,6 @@ config TASKS_RCU
           only voluntary context switch (not preemption!), idle, and
           user-mode execution as quiescent states.
 
-          If unsure, say N.
-
 config RCU_STALL_COMMON
         def_bool ( TREE_RCU || PREEMPT_RCU || RCU_TRACE )
         help