| .. | .. | 
|---|
 | 1 | +# SPDX-License-Identifier: GPL-2.0-only  | 
|---|
| 1 | 2 |  # | 
|---|
| 2 | 3 |  # Timer subsystem related configuration options | 
|---|
| 3 | 4 |  # | 
|---|
| .. | .. | 
|---|
| 10 | 11 |   | 
|---|
| 11 | 12 |  # Architecture has extra clocksource data | 
|---|
| 12 | 13 |  config ARCH_CLOCKSOURCE_DATA | 
|---|
 | 14 | +	bool  | 
|---|
 | 15 | +  | 
|---|
 | 16 | +# Architecture has extra clocksource init called from registration  | 
|---|
 | 17 | +config ARCH_CLOCKSOURCE_INIT  | 
|---|
| 13 | 18 |  	bool | 
|---|
| 14 | 19 |   | 
|---|
| 15 | 20 |  # Clocksources require validation of the clocksource against the last | 
|---|
| .. | .. | 
|---|
| 46 | 51 |  # Generic update of CMOS clock | 
|---|
| 47 | 52 |  config GENERIC_CMOS_UPDATE | 
|---|
| 48 | 53 |  	bool | 
|---|
 | 54 | +  | 
|---|
 | 55 | +# Select to handle posix CPU timers from task_work  | 
|---|
 | 56 | +# and not from the timer interrupt context  | 
|---|
 | 57 | +config HAVE_POSIX_CPU_TIMERS_TASK_WORK  | 
|---|
 | 58 | +	bool  | 
|---|
 | 59 | +  | 
|---|
 | 60 | +config POSIX_CPU_TIMERS_TASK_WORK  | 
|---|
 | 61 | +	bool  | 
|---|
 | 62 | +	default y if POSIX_TIMERS && HAVE_POSIX_CPU_TIMERS_TASK_WORK  | 
|---|
| 49 | 63 |   | 
|---|
| 50 | 64 |  if GENERIC_CLOCKEVENTS | 
|---|
| 51 | 65 |  menu "Timers subsystem" | 
|---|
| .. | .. | 
|---|
| 113 | 127 |   | 
|---|
| 114 | 128 |  endchoice | 
|---|
| 115 | 129 |   | 
|---|
 | 130 | +config CONTEXT_TRACKING  | 
|---|
 | 131 | +       bool  | 
|---|
 | 132 | +  | 
|---|
 | 133 | +config CONTEXT_TRACKING_FORCE  | 
|---|
 | 134 | +	bool "Force context tracking"  | 
|---|
 | 135 | +	depends on CONTEXT_TRACKING  | 
|---|
 | 136 | +	default y if !NO_HZ_FULL  | 
|---|
 | 137 | +	help  | 
|---|
 | 138 | +	  The major pre-requirement for full dynticks to work is to  | 
|---|
 | 139 | +	  support the context tracking subsystem. But there are also  | 
|---|
 | 140 | +	  other dependencies to provide in order to make the full  | 
|---|
 | 141 | +	  dynticks working.  | 
|---|
 | 142 | +  | 
|---|
 | 143 | +	  This option stands for testing when an arch implements the  | 
|---|
 | 144 | +	  context tracking backend but doesn't yet fullfill all the  | 
|---|
 | 145 | +	  requirements to make the full dynticks feature working.  | 
|---|
 | 146 | +	  Without the full dynticks, there is no way to test the support  | 
|---|
 | 147 | +	  for context tracking and the subsystems that rely on it: RCU  | 
|---|
 | 148 | +	  userspace extended quiescent state and tickless cputime  | 
|---|
 | 149 | +	  accounting. This option copes with the absence of the full  | 
|---|
 | 150 | +	  dynticks subsystem by forcing the context tracking on all  | 
|---|
 | 151 | +	  CPUs in the system.  | 
|---|
 | 152 | +  | 
|---|
 | 153 | +	  Say Y only if you're working on the development of an  | 
|---|
 | 154 | +	  architecture backend for the context tracking.  | 
|---|
 | 155 | +  | 
|---|
 | 156 | +	  Say N otherwise, this option brings an overhead that you  | 
|---|
 | 157 | +	  don't want in production.  | 
|---|
 | 158 | +  | 
|---|
| 116 | 159 |  config NO_HZ | 
|---|
| 117 | 160 |  	bool "Old Idle dynticks config" | 
|---|
| 118 | 161 |  	depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS | 
|---|