From 82d0f4c089991e6b302d961f0320282bf91652d7 Mon Sep 17 00:00:00 2001 From: "Paul E. McKenney" Date: Mon, 20 Apr 2015 05:42:50 -0700 Subject: 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 Signed-off-by: Paul E. McKenney Cc: Steven Rostedt Reviewed-by: Pranith Kumar --- init/Kconfig | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'init/Kconfig') 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 -- cgit v1.2.3-59-g8ed1b