summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2015-04-20 06:17:15 -0700
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2015-05-27 12:59:03 -0700
commit7db21edfecb079b2257ced7a2cf2e32ae5e5d966 (patch)
treebd4faba7a9f53c1aff2b4b6faf7a1d0b0a3205f3 /init
parent82d0f4c089991e6b302d961f0320282bf91652d7 (diff)
downloadlinux-7db21edfecb079b2257ced7a2cf2e32ae5e5d966.tar.gz
linux-7db21edfecb079b2257ced7a2cf2e32ae5e5d966.tar.bz2
linux-7db21edfecb079b2257ced7a2cf2e32ae5e5d966.zip
rcu: Directly drive RCU_USER_QS from Kconfig
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. Reported-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Reviewed-by: Pranith Kumar <bobby.prani@gmail.com> Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Diffstat (limited to 'init')
-rw-r--r--init/Kconfig10
1 files changed, 1 insertions, 9 deletions
diff --git a/init/Kconfig b/init/Kconfig
index 73db30a76afa..927210810189 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -529,9 +529,7 @@ config CONTEXT_TRACKING
bool
config RCU_USER_QS
- bool "Consider userspace as in RCU extended quiescent state"
- depends on HAVE_CONTEXT_TRACKING && SMP
- select CONTEXT_TRACKING
+ bool
help
This option sets hooks on kernel / userspace boundaries and
puts RCU in extended quiescent state when the CPU runs in
@@ -539,12 +537,6 @@ config RCU_USER_QS
excluded from the global RCU state machine and thus doesn't
try to keep the timer tick on for RCU.
- Unless you want to hack and help the development of the full
- dynticks mode, you shouldn't enable this option. It also
- adds unnecessary overhead.
-
- If unsure say N
-
config CONTEXT_TRACKING_FORCE
bool "Force context tracking"
depends on CONTEXT_TRACKING