mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 11:11:45 -04:00
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 <[email protected]> Signed-off-by: Paul E. McKenney <[email protected]> Cc: Steven Rostedt <[email protected]> Reviewed-by: Pranith Kumar <[email protected]>
This commit is contained in:
parent
0f41c0ddad
commit
82d0f4c089
2 changed files with 2 additions and 3 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue