blob: e2c038d6c13cdaecc07c113becb831443f92269d [file] [log] [blame]
Thomas Gleixner79bf2bb2007-02-16 01:28:03 -08001#
2# Timer subsystem related configuration options
3#
Thomas Gleixner3872c482012-03-31 12:45:43 +02004
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +02005# Options selectable by arch Kconfig
6
7# Watchdog function for clocksources to detect instabilities
8config CLOCKSOURCE_WATCHDOG
9 bool
10
11# Architecture has extra clocksource data
12config ARCH_CLOCKSOURCE_DATA
13 bool
14
Thomas Gleixnerd67f34c2018-09-17 14:45:34 +020015# Architecture has extra clocksource init called from registration
16config ARCH_CLOCKSOURCE_INIT
17 bool
18
Thomas Gleixner09ec5442014-07-16 21:05:12 +000019# Clocksources require validation of the clocksource against the last
20# cycle update - x86/TSC misfeature
21config CLOCKSOURCE_VALIDATE_LAST_CYCLE
22 bool
23
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020024# Timekeeping vsyscall support
John Stultz576094b2012-09-11 19:58:13 -040025config GENERIC_TIME_VSYSCALL
26 bool
27
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020028# Old style timekeeping
29config ARCH_USES_GETTIMEOFFSET
30 bool
31
32# The generic clock events infrastructure
33config GENERIC_CLOCKEVENTS
34 bool
35
Mark Rutland12ad1002013-01-14 17:05:22 +000036# Architecture can handle broadcast in a driver-agnostic way
37config ARCH_HAS_TICK_BROADCAST
38 bool
39
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020040# Clockevents broadcasting infrastructure
41config GENERIC_CLOCKEVENTS_BROADCAST
42 bool
43 depends on GENERIC_CLOCKEVENTS
44
Thomas Gleixner764e0da2012-05-21 23:16:18 +020045# Automatically adjust the min. reprogramming time for
46# clock event device
47config GENERIC_CLOCKEVENTS_MIN_ADJUST
48 bool
49
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020050# Generic update of CMOS clock
51config GENERIC_CMOS_UPDATE
52 bool
Thomas Gleixner764e0da2012-05-21 23:16:18 +020053
54if GENERIC_CLOCKEVENTS
55menu "Timers subsystem"
56
Frederic Weisbecker3451d022011-08-10 23:21:01 +020057# Core internal switch. Selected by NO_HZ_COMMON / HIGH_RES_TIMERS. This is
Thomas Gleixner764e0da2012-05-21 23:16:18 +020058# only related to the tick functionality. Oneshot clockevent devices
Randy Dunlap6082a6e2017-11-01 11:04:51 -070059# are supported independent of this.
Thomas Gleixner764e0da2012-05-21 23:16:18 +020060config TICK_ONESHOT
61 bool
62
Frederic Weisbecker3451d022011-08-10 23:21:01 +020063config NO_HZ_COMMON
64 bool
65 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
66 select TICK_ONESHOT
67
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +020068choice
69 prompt "Timer tick handling"
70 default NO_HZ_IDLE if NO_HZ
71
Frederic Weisbecker5b533f42013-04-13 16:53:35 +020072config HZ_PERIODIC
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +020073 bool "Periodic timer ticks (constant rate, no dynticks)"
74 help
75 This option keeps the tick running periodically at a constant
76 rate, even when the CPU doesn't need it.
77
78config NO_HZ_IDLE
79 bool "Idle dynticks system (tickless idle)"
Thomas Gleixner764e0da2012-05-21 23:16:18 +020080 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
Frederic Weisbecker3451d022011-08-10 23:21:01 +020081 select NO_HZ_COMMON
Thomas Gleixner764e0da2012-05-21 23:16:18 +020082 help
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +020083 This option enables a tickless idle system: timer interrupts
84 will only trigger on an as-needed basis when the system is idle.
85 This is usually interesting for energy saving.
86
87 Most of the time you want to say Y here.
Thomas Gleixner764e0da2012-05-21 23:16:18 +020088
Frederic Weisbeckerc5bfece2013-04-12 16:45:34 +020089config NO_HZ_FULL
Frederic Weisbeckerfae30dd2013-04-13 17:04:04 +020090 bool "Full dynticks system (tickless)"
Frederic Weisbecker3451d022011-08-10 23:21:01 +020091 # NO_HZ_COMMON dependency
Frederic Weisbeckerab71d362011-08-10 23:21:01 +020092 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
Frederic Weisbeckerfae30dd2013-04-13 17:04:04 +020093 # We need at least one periodic CPU for timekeeping
94 depends on SMP
Frederic Weisbeckerfae30dd2013-04-13 17:04:04 +020095 depends on HAVE_CONTEXT_TRACKING
Frederic Weisbeckerc58b0df2013-04-26 15:16:31 +020096 # VIRT_CPU_ACCOUNTING_GEN dependency
Kevin Hilman554b0002013-09-16 15:28:21 -070097 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
Frederic Weisbecker3451d022011-08-10 23:21:01 +020098 select NO_HZ_COMMON
Frederic Weisbeckerab71d362011-08-10 23:21:01 +020099 select RCU_NOCB_CPU
Frederic Weisbeckerc58b0df2013-04-26 15:16:31 +0200100 select VIRT_CPU_ACCOUNTING_GEN
Frederic Weisbecker76c24fb2013-04-18 00:15:40 +0200101 select IRQ_WORK
Paul E. McKenneybf29cb22017-12-14 19:18:25 +0100102 select CPU_ISOLATION
Frederic Weisbeckerab71d362011-08-10 23:21:01 +0200103 help
104 Adaptively try to shutdown the tick whenever possible, even when
Frederic Weisbeckera8318812012-12-18 17:32:19 +0100105 the CPU is running tasks. Typically this requires running a single
106 task on the CPU. Chances for running tickless are maximized when
107 the task mostly runs in userspace and has few kernel activity.
108
Frederic Weisbeckerc5bfece2013-04-12 16:45:34 +0200109 You need to fill up the nohz_full boot parameter with the
Frederic Weisbeckera8318812012-12-18 17:32:19 +0100110 desired range of dynticks CPUs.
111
112 This is implemented at the expense of some overhead in user <-> kernel
113 transitions: syscalls, exceptions and interrupts. Even when it's
114 dynamically off.
115
116 Say N.
117
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +0200118endchoice
119
Paul E. McKenneya4cffda2018-12-20 09:05:25 -0800120config CONTEXT_TRACKING
121 bool
122
123config CONTEXT_TRACKING_FORCE
124 bool "Force context tracking"
125 depends on CONTEXT_TRACKING
126 default y if !NO_HZ_FULL
127 help
128 The major pre-requirement for full dynticks to work is to
129 support the context tracking subsystem. But there are also
130 other dependencies to provide in order to make the full
131 dynticks working.
132
133 This option stands for testing when an arch implements the
134 context tracking backend but doesn't yet fullfill all the
135 requirements to make the full dynticks feature working.
136 Without the full dynticks, there is no way to test the support
137 for context tracking and the subsystems that rely on it: RCU
138 userspace extended quiescent state and tickless cputime
139 accounting. This option copes with the absence of the full
140 dynticks subsystem by forcing the context tracking on all
141 CPUs in the system.
142
143 Say Y only if you're working on the development of an
144 architecture backend for the context tracking.
145
146 Say N otherwise, this option brings an overhead that you
147 don't want in production.
148
Frederic Weisbecker0644ca52013-04-12 16:40:12 +0200149config NO_HZ
150 bool "Old Idle dynticks config"
151 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
152 help
153 This is the old config entry that enables dynticks idle.
154 We keep it around for a little while to enforce backward
155 compatibility with older config files.
156
Thomas Gleixner764e0da2012-05-21 23:16:18 +0200157config HIGH_RES_TIMERS
158 bool "High Resolution Timer Support"
159 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
160 select TICK_ONESHOT
161 help
162 This option enables high resolution timer support. If your
163 hardware is not capable then this option only increases
164 the size of the kernel image.
165
166endmenu
167endif