blob: 83e158d016bada24d9fa2ed5126bfc5551351966 [file] [log] [blame]
Thomas Gleixnerec8f24b2019-05-19 13:07:45 +01001# SPDX-License-Identifier: GPL-2.0-only
Thomas Gleixner79bf2bb2007-02-16 01:28:03 -08002#
3# Timer subsystem related configuration options
4#
Thomas Gleixner3872c482012-03-31 12:45:43 +02005
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +02006# Options selectable by arch Kconfig
7
8# Watchdog function for clocksources to detect instabilities
9config CLOCKSOURCE_WATCHDOG
10 bool
11
12# Architecture has extra clocksource data
13config ARCH_CLOCKSOURCE_DATA
14 bool
15
Thomas Gleixnerd67f34c2018-09-17 14:45:34 +020016# Architecture has extra clocksource init called from registration
17config ARCH_CLOCKSOURCE_INIT
18 bool
19
Thomas Gleixner09ec5442014-07-16 21:05:12 +000020# Clocksources require validation of the clocksource against the last
21# cycle update - x86/TSC misfeature
22config CLOCKSOURCE_VALIDATE_LAST_CYCLE
23 bool
24
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020025# Timekeeping vsyscall support
John Stultz576094b2012-09-11 19:58:13 -040026config GENERIC_TIME_VSYSCALL
27 bool
28
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020029# The generic clock events infrastructure
30config GENERIC_CLOCKEVENTS
Arnd Bergmann0774a6ed2020-09-24 11:32:40 +020031 def_bool !LEGACY_TIMER_TICK
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020032
Mark Rutland12ad1002013-01-14 17:05:22 +000033# Architecture can handle broadcast in a driver-agnostic way
34config ARCH_HAS_TICK_BROADCAST
35 bool
36
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020037# Clockevents broadcasting infrastructure
38config GENERIC_CLOCKEVENTS_BROADCAST
39 bool
40 depends on GENERIC_CLOCKEVENTS
41
Thomas Gleixner764e0da2012-05-21 23:16:18 +020042# Automatically adjust the min. reprogramming time for
43# clock event device
44config GENERIC_CLOCKEVENTS_MIN_ADJUST
45 bool
46
Thomas Gleixnerb5e498a2012-05-18 09:59:57 +020047# Generic update of CMOS clock
48config GENERIC_CMOS_UPDATE
49 bool
Thomas Gleixner764e0da2012-05-21 23:16:18 +020050
Thomas Gleixner1fb497d2020-07-30 12:14:06 +020051# Select to handle posix CPU timers from task_work
52# and not from the timer interrupt context
53config HAVE_POSIX_CPU_TIMERS_TASK_WORK
54 bool
55
56config POSIX_CPU_TIMERS_TASK_WORK
57 bool
58 default y if POSIX_TIMERS && HAVE_POSIX_CPU_TIMERS_TASK_WORK
59
Arnd Bergmannb3550162020-09-24 15:21:43 +020060config LEGACY_TIMER_TICK
61 bool
62 help
63 The legacy timer tick helper is used by platforms that
64 lack support for the generic clockevent framework.
65 New platforms should use generic clockevents instead.
66
Thomas Gleixner764e0da2012-05-21 23:16:18 +020067if GENERIC_CLOCKEVENTS
68menu "Timers subsystem"
69
Frederic Weisbecker3451d022011-08-10 23:21:01 +020070# Core internal switch. Selected by NO_HZ_COMMON / HIGH_RES_TIMERS. This is
Thomas Gleixner764e0da2012-05-21 23:16:18 +020071# only related to the tick functionality. Oneshot clockevent devices
Randy Dunlap6082a6e2017-11-01 11:04:51 -070072# are supported independent of this.
Thomas Gleixner764e0da2012-05-21 23:16:18 +020073config TICK_ONESHOT
74 bool
75
Frederic Weisbecker3451d022011-08-10 23:21:01 +020076config NO_HZ_COMMON
77 bool
Frederic Weisbecker3451d022011-08-10 23:21:01 +020078 select TICK_ONESHOT
79
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +020080choice
81 prompt "Timer tick handling"
82 default NO_HZ_IDLE if NO_HZ
83
Frederic Weisbecker5b533f42013-04-13 16:53:35 +020084config HZ_PERIODIC
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +020085 bool "Periodic timer ticks (constant rate, no dynticks)"
86 help
87 This option keeps the tick running periodically at a constant
88 rate, even when the CPU doesn't need it.
89
90config NO_HZ_IDLE
91 bool "Idle dynticks system (tickless idle)"
Frederic Weisbecker3451d022011-08-10 23:21:01 +020092 select NO_HZ_COMMON
Thomas Gleixner764e0da2012-05-21 23:16:18 +020093 help
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +020094 This option enables a tickless idle system: timer interrupts
95 will only trigger on an as-needed basis when the system is idle.
96 This is usually interesting for energy saving.
97
98 Most of the time you want to say Y here.
Thomas Gleixner764e0da2012-05-21 23:16:18 +020099
Frederic Weisbeckerc5bfece2013-04-12 16:45:34 +0200100config NO_HZ_FULL
Frederic Weisbeckerfae30dd2013-04-13 17:04:04 +0200101 bool "Full dynticks system (tickless)"
Frederic Weisbecker3451d022011-08-10 23:21:01 +0200102 # NO_HZ_COMMON dependency
Frederic Weisbeckerfae30dd2013-04-13 17:04:04 +0200103 # We need at least one periodic CPU for timekeeping
104 depends on SMP
Frederic Weisbeckerfae30dd2013-04-13 17:04:04 +0200105 depends on HAVE_CONTEXT_TRACKING
Frederic Weisbeckerc58b0df2013-04-26 15:16:31 +0200106 # VIRT_CPU_ACCOUNTING_GEN dependency
Kevin Hilman554b0002013-09-16 15:28:21 -0700107 depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
Frederic Weisbecker3451d022011-08-10 23:21:01 +0200108 select NO_HZ_COMMON
Frederic Weisbeckerab71d362011-08-10 23:21:01 +0200109 select RCU_NOCB_CPU
Frederic Weisbeckerc58b0df2013-04-26 15:16:31 +0200110 select VIRT_CPU_ACCOUNTING_GEN
Frederic Weisbecker76c24fb2013-04-18 00:15:40 +0200111 select IRQ_WORK
Paul E. McKenneybf29cb22017-12-14 19:18:25 +0100112 select CPU_ISOLATION
Frederic Weisbeckerab71d362011-08-10 23:21:01 +0200113 help
114 Adaptively try to shutdown the tick whenever possible, even when
Frederic Weisbeckera8318812012-12-18 17:32:19 +0100115 the CPU is running tasks. Typically this requires running a single
116 task on the CPU. Chances for running tickless are maximized when
117 the task mostly runs in userspace and has few kernel activity.
118
Frederic Weisbeckerc5bfece2013-04-12 16:45:34 +0200119 You need to fill up the nohz_full boot parameter with the
Frederic Weisbeckera8318812012-12-18 17:32:19 +0100120 desired range of dynticks CPUs.
121
122 This is implemented at the expense of some overhead in user <-> kernel
123 transitions: syscalls, exceptions and interrupts. Even when it's
124 dynamically off.
125
126 Say N.
127
Frederic Weisbecker3ca277e2011-08-10 23:21:01 +0200128endchoice
129
Paul E. McKenneya4cffda2018-12-20 09:05:25 -0800130config CONTEXT_TRACKING
131 bool
132
133config 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
Colin Ian Kingf6f5cd842020-12-17 17:17:05 +0000144 context tracking backend but doesn't yet fulfill all the
Paul E. McKenneya4cffda2018-12-20 09:05:25 -0800145 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
Frederic Weisbecker0644ca52013-04-12 16:40:12 +0200159config NO_HZ
160 bool "Old Idle dynticks config"
Frederic Weisbecker0644ca52013-04-12 16:40:12 +0200161 help
162 This is the old config entry that enables dynticks idle.
163 We keep it around for a little while to enforce backward
164 compatibility with older config files.
165
Thomas Gleixner764e0da2012-05-21 23:16:18 +0200166config HIGH_RES_TIMERS
167 bool "High Resolution Timer Support"
Thomas Gleixner764e0da2012-05-21 23:16:18 +0200168 select TICK_ONESHOT
169 help
170 This option enables high resolution timer support. If your
171 hardware is not capable then this option only increases
172 the size of the kernel image.
173
174endmenu
175endif