time: Move CONTEXT_TRACKING to kernel/time/Kconfig

Both CONTEXT_TRACKING and CONTEXT_TRACKING_FORCE are currently defined
in kernel/rcu/kconfig, which might have made sense at some point, but
no longer does given that RCU refers to neither of these Kconfig options.

Therefore move them to kernel/time/Kconfig, where the rest of the
NO_HZ_FULL Kconfig options live.

Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Link: https://lkml.kernel.org/r/20181220170525.GA12579@linux.ibm.com

diff --git a/kernel/rcu/Kconfig b/kernel/rcu/Kconfig
index 939a2056c87a878ce7e9c1eebd652b5dd20ef1be..37301430970e4b9fc7e13ae26627571577ae0db0 100644 (file)
--- a/kernel/rcu/Kconfig
+++ b/kernel/rcu/Kconfig
@@ -87,36 +87,6 @@ config RCU_STALL_COMMON
 config RCU_NEED_SEGCBLIST
        def_bool ( TREE_RCU || PREEMPT_RCU || TREE_SRCU )
 
-config CONTEXT_TRACKING
-       bool
-
-config CONTEXT_TRACKING_FORCE
-       bool "Force context tracking"
-       depends on CONTEXT_TRACKING
-       default y if !NO_HZ_FULL
-       help
-         The major pre-requirement for full dynticks to work is to
-         support the context tracking subsystem. But there are also
-         other dependencies to provide in order to make the full
-         dynticks working.
-
-         This option stands for testing when an arch implements the
-         context tracking backend but doesn't yet fullfill all the
-         requirements to make the full dynticks feature working.
-         Without the full dynticks, there is no way to test the support
-         for context tracking and the subsystems that rely on it: RCU
-         userspace extended quiescent state and tickless cputime
-         accounting. This option copes with the absence of the full
-         dynticks subsystem by forcing the context tracking on all
-         CPUs in the system.
-
-         Say Y only if you're working on the development of an
-         architecture backend for the context tracking.
-
-         Say N otherwise, this option brings an overhead that you
-         don't want in production.
-
-
 config RCU_FANOUT
        int "Tree-based hierarchical RCU fanout value"
        range 2 64 if 64BIT

diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
index 58b981f4bb5d72b7adf0a1745fe481fb1b6df39d..e2c038d6c13cdaecc07c113becb831443f92269d 100644 (file)
--- a/kernel/time/Kconfig
+++ b/kernel/time/Kconfig
@@ -117,6 +117,35 @@ config NO_HZ_FULL
 
 endchoice
 
+config CONTEXT_TRACKING
+       bool
+
+config CONTEXT_TRACKING_FORCE
+       bool "Force context tracking"
+       depends on CONTEXT_TRACKING
+       default y if !NO_HZ_FULL
+       help
+         The major pre-requirement for full dynticks to work is to
+         support the context tracking subsystem. But there are also
+         other dependencies to provide in order to make the full
+         dynticks working.
+
+         This option stands for testing when an arch implements the
+         context tracking backend but doesn't yet fullfill all the
+         requirements to make the full dynticks feature working.
+         Without the full dynticks, there is no way to test the support
+         for context tracking and the subsystems that rely on it: RCU
+         userspace extended quiescent state and tickless cputime
+         accounting. This option copes with the absence of the full
+         dynticks subsystem by forcing the context tracking on all
+         CPUs in the system.
+
+         Say Y only if you're working on the development of an
+         architecture backend for the context tracking.
+
+         Say N otherwise, this option brings an overhead that you
+         don't want in production.
+
 config NO_HZ
        bool "Old Idle dynticks config"
        depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS