#
# Timer subsystem related configuration options
#
# Options selectable by arch Kconfig
# Watchdog function for clocksources to detect instabilities
config [31mCONFIG_CLOCKSOURCE_WATCHDOG[0m
bool
# Architecture has extra clocksource data
config [31mCONFIG_ARCH_CLOCKSOURCE_DATA[0m
bool
# Clocksources require validation of the clocksource against the last
# cycle update - x86/TSC misfeature
config [31mCONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE[0m
bool
# Timekeeping vsyscall support
config [31mCONFIG_GENERIC_TIME_VSYSCALL[0m
bool
# Timekeeping vsyscall support
config [31mCONFIG_GENERIC_TIME_VSYSCALL_OLD[0m
bool
# Old style timekeeping
config [31mCONFIG_ARCH_USES_GETTIMEOFFSET[0m
bool
# The generic clock events infrastructure
config [31mCONFIG_GENERIC_CLOCKEVENTS[0m
bool
# Architecture can handle broadcast in a driver-agnostic way
config [31mCONFIG_ARCH_HAS_TICK_BROADCAST[0m
bool
# Clockevents broadcasting infrastructure
config [31mCONFIG_GENERIC_CLOCKEVENTS_BROADCAST[0m
bool
depends on [31mCONFIG_GENERIC_CLOCKEVENTS[0m
# Automatically adjust the min. reprogramming time for
# clock event device
config [31mCONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST[0m
bool
# Generic update of CMOS clock
config [31mCONFIG_GENERIC_CMOS_UPDATE[0m
bool
if [31mCONFIG_GENERIC_CLOCKEVENTS[0m
menu "Timers subsystem"
# Core internal switch. Selected by [31mCONFIG_NO_HZ_COMMON[0m / [31mCONFIG_HIGH_RES_TIMERS[0m. This is
# only related to the tick functionality. Oneshot clockevent devices
# are supported independ of this.
config [31mCONFIG_TICK_ONESHOT[0m
bool
config [31mCONFIG_NO_HZ_COMMON[0m
bool
depends on ![31mCONFIG_ARCH_USES_GETTIMEOFFSET[0m && [31mCONFIG_GENERIC_CLOCKEVENTS[0m
select [31mCONFIG_TICK_ONESHOT[0m
choice
prompt "Timer tick handling"
default [31mCONFIG_NO_HZ_IDLE[0m if [31mCONFIG_NO_HZ[0m
config [31mCONFIG_HZ_PERIODIC[0m
bool "Periodic timer ticks (constant rate, no dynticks)"
help
This option keeps the tick running periodically at a constant
rate, even when the CPU doesn't need it.
config [31mCONFIG_NO_HZ_IDLE[0m
bool "Idle dynticks system (tickless idle)"
depends on ![31mCONFIG_ARCH_USES_GETTIMEOFFSET[0m && [31mCONFIG_GENERIC_CLOCKEVENTS[0m
select [31mCONFIG_NO_HZ_COMMON[0m
help
This option enables a tickless idle system: timer interrupts
will only trigger on an as-needed basis when the system is idle.
This is usually interesting for energy saving.
Most of the time you want to say Y here.
config [31mCONFIG_NO_HZ_FULL[0m
bool "Full dynticks system (tickless)"
# [31mCONFIG_NO_HZ_COMMON[0m dependency
depends on ![31mCONFIG_ARCH_USES_GETTIMEOFFSET[0m && [31mCONFIG_GENERIC_CLOCKEVENTS[0m
# We need at least one periodic CPU for timekeeping
depends on [31mCONFIG_SMP[0m
depends on [31mCONFIG_HAVE_CONTEXT_TRACKING[0m
# [31mCONFIG_VIRT_CPU_ACCOUNTING_GEN[0m dependency
depends on [31mCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN[0m
select [31mCONFIG_NO_HZ_COMMON[0m
select [31mCONFIG_RCU_NOCB_CPU[0m
select [31mCONFIG_VIRT_CPU_ACCOUNTING_GEN[0m
select [31mCONFIG_IRQ_WORK[0m
help
Adaptively try to shutdown the tick whenever possible, even when
the CPU is running tasks. Typically this requires running a single
task on the CPU. Chances for running tickless are maximized when
the task mostly runs in userspace and has few kernel activity.
You need to fill up the nohz_full boot parameter with the
desired range of dynticks CPUs.
This is implemented at the expense of some overhead in user <-> kernel
transitions: syscalls, exceptions and interrupts. Even when it's
dynamically off.
Say N.
endchoice
config [31mCONFIG_NO_HZ_FULL_ALL[0m
bool "Full dynticks system on all CPUs by default (except CPU 0)"
depends on [31mCONFIG_NO_HZ_FULL[0m
help
If the user doesn't pass the nohz_full boot option to
define the range of full dynticks CPUs, consider that all
CPUs in the system are full dynticks by default.
Note the boot CPU will still be kept outside the range to
handle the timekeeping duty.
config [31mCONFIG_NO_HZ_FULL_SYSIDLE[0m
bool "Detect full-system idle state for full dynticks system"
depends on [31mCONFIG_NO_HZ_FULL[0m
default n
help
At least one CPU must keep the scheduling-clock tick running for
timekeeping purposes whenever there is a non-idle CPU, where
"non-idle" also includes dynticks CPUs as long as they are
running non-idle tasks. Because the underlying adaptive-tick
support cannot distinguish between all CPUs being idle and
all CPUs each running a single task in dynticks mode, the
underlying support simply ensures that there is always a CPU
handling the scheduling-clock tick, whether or not all CPUs
are idle. This Kconfig option enables scalable detection of
the all-CPUs-idle state, thus allowing the scheduling-clock
tick to be disabled when all CPUs are idle. Note that scalable
detection of the all-CPUs-idle state means that larger systems
will be slower to declare the all-CPUs-idle state.
Say Y if you would like to help debug all-CPUs-idle detection.
Say N if you are unsure.
config [31mCONFIG_NO_HZ_FULL_SYSIDLE_SMALL[0m
int "Number of CPUs above which large-system approach is used"
depends on [31mCONFIG_NO_HZ_FULL_SYSIDLE[0m
range 1 [31mCONFIG_NR_CPUS[0m
default 8
help
The full-system idle detection mechanism takes a lazy approach
on large systems, as is required to attain decent scalability.
However, on smaller systems, scalability is not anywhere near as
large a concern as is energy efficiency. The sysidle subsystem
therefore uses a fast but non-scalable algorithm for small
systems and a lazier but scalable algorithm for large systems.
This Kconfig parameter defines the number of CPUs in the largest
system that will be considered to be "small".
The default value will be fine in most cases. Battery-powered
systems that (1) enable [31mCONFIG_NO_HZ_FULL_SYSIDLE[0m, (2) have larger
numbers of CPUs, and (3) are suffering from battery-lifetime
problems due to long sysidle latencies might wish to experiment
with larger values for this Kconfig parameter. On the other
hand, they might be even better served by disabling [31mCONFIG_NO_HZ_FULL[0m
entirely, given that [31mCONFIG_NO_HZ_FULL[0m is intended for HPC and
real-time workloads that at present do not tend to be run on
battery-powered systems.
Take the default if you are unsure.
config [31mCONFIG_NO_HZ[0m
bool "Old Idle dynticks config"
depends on ![31mCONFIG_ARCH_USES_GETTIMEOFFSET[0m && [31mCONFIG_GENERIC_CLOCKEVENTS[0m
help
This is the old config entry that enables dynticks idle.
We keep it around for a little while to enforce backward
compatibility with older config files.
config [31mCONFIG_HIGH_RES_TIMERS[0m
bool "High Resolution Timer Support"
depends on ![31mCONFIG_ARCH_USES_GETTIMEOFFSET[0m && [31mCONFIG_GENERIC_CLOCKEVENTS[0m
select [31mCONFIG_TICK_ONESHOT[0m
help
This option enables high resolution timer support. If your
hardware is not capable then this option only increases
the size of the kernel image.
endmenu
endif