2 # Timer subsystem related configuration options
5 # Options selectable by arch Kconfig
7 # Watchdog function for clocksources to detect instabilities
8 config CLOCKSOURCE_WATCHDOG
11 # Architecture has extra clocksource data
12 config ARCH_CLOCKSOURCE_DATA
15 # Platforms has a persistent clock
16 config ALWAYS_USE_PERSISTENT_CLOCK
20 # Timekeeping vsyscall support
21 config GENERIC_TIME_VSYSCALL
24 # Timekeeping vsyscall support
25 config GENERIC_TIME_VSYSCALL_OLD
28 # ktime_t scalar 64bit nsec representation
32 # Old style timekeeping
33 config ARCH_USES_GETTIMEOFFSET
36 # The generic clock events infrastructure
37 config GENERIC_CLOCKEVENTS
40 # Migration helper. Builds, but does not invoke
41 config GENERIC_CLOCKEVENTS_BUILD
44 depends on GENERIC_CLOCKEVENTS
46 # Architecture can handle broadcast in a driver-agnostic way
47 config ARCH_HAS_TICK_BROADCAST
50 # Clockevents broadcasting infrastructure
51 config GENERIC_CLOCKEVENTS_BROADCAST
53 depends on GENERIC_CLOCKEVENTS
55 # Automatically adjust the min. reprogramming time for
57 config GENERIC_CLOCKEVENTS_MIN_ADJUST
60 # Generic update of CMOS clock
61 config GENERIC_CMOS_UPDATE
64 if GENERIC_CLOCKEVENTS
65 menu "Timers subsystem"
67 # Core internal switch. Selected by NO_HZ / HIGH_RES_TIMERS. This is
68 # only related to the tick functionality. Oneshot clockevent devices
69 # are supported independ of this.
74 bool "Tickless System (Dynamic Ticks)"
75 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
78 This option enables a tickless system: timer interrupts will
79 only trigger on an as-needed basis both when the system is
80 busy and when the system is idle.
83 bool "Full dynticks system"
84 depends on NO_HZ && RCU_USER_QS && VIRT_CPU_ACCOUNTING_GEN && RCU_NOCB_CPU && SMP
85 select CONTEXT_TRACKING_FORCE
87 Adaptively try to shutdown the tick whenever possible, even when
88 the CPU is running tasks. Typically this requires running a single
89 task on the CPU. Chances for running tickless are maximized when
90 the task mostly runs in userspace and has few kernel activity.
92 You need to fill up the nohz_extended boot parameter with the
93 desired range of dynticks CPUs.
95 This is implemented at the expense of some overhead in user <-> kernel
96 transitions: syscalls, exceptions and interrupts. Even when it's
101 config HIGH_RES_TIMERS
102 bool "High Resolution Timer Support"
103 depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
106 This option enables high resolution timer support. If your
107 hardware is not capable then this option only increases
108 the size of the kernel image.