Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a4cffdad authored by Paul E. McKenney's avatar Paul E. McKenney Committed by Thomas Gleixner
Browse files

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: default avatarPaul E. McKenney <paulmck@linux.ibm.com>
Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Link: https://lkml.kernel.org/r/20181220170525.GA12579@linux.ibm.com
parent 1c7fc5cb

kernel/rcu/Kconfig

+0 −30
Original line number Diff line number Diff line
@@ -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

kernel/time/Kconfig

+29 −0
Original line number Diff line number Diff line
@@ -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