2007-02-16 17:28:03 +08:00
|
|
|
#
|
|
|
|
|
# Timer subsystem related configuration options
|
|
|
|
|
#
|
2012-03-31 18:45:43 +08:00
|
|
|
|
2012-05-18 15:59:57 +08:00
|
|
|
# Options selectable by arch Kconfig
|
|
|
|
|
|
|
|
|
|
# Watchdog function for clocksources to detect instabilities
|
|
|
|
|
config CLOCKSOURCE_WATCHDOG
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
# Architecture has extra clocksource data
|
|
|
|
|
config ARCH_CLOCKSOURCE_DATA
|
|
|
|
|
bool
|
|
|
|
|
|
2014-07-17 05:05:12 +08:00
|
|
|
# Clocksources require validation of the clocksource against the last
|
|
|
|
|
# cycle update - x86/TSC misfeature
|
|
|
|
|
config CLOCKSOURCE_VALIDATE_LAST_CYCLE
|
|
|
|
|
bool
|
|
|
|
|
|
2012-09-12 07:58:13 +08:00
|
|
|
# Timekeeping vsyscall support
|
|
|
|
|
config GENERIC_TIME_VSYSCALL
|
|
|
|
|
bool
|
|
|
|
|
|
2012-05-18 15:59:57 +08:00
|
|
|
# Timekeeping vsyscall support
|
2012-09-05 03:34:21 +08:00
|
|
|
config GENERIC_TIME_VSYSCALL_OLD
|
2012-05-18 15:59:57 +08:00
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
# Old style timekeeping
|
|
|
|
|
config ARCH_USES_GETTIMEOFFSET
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
# The generic clock events infrastructure
|
|
|
|
|
config GENERIC_CLOCKEVENTS
|
|
|
|
|
bool
|
|
|
|
|
|
2013-01-15 01:05:22 +08:00
|
|
|
# Architecture can handle broadcast in a driver-agnostic way
|
|
|
|
|
config ARCH_HAS_TICK_BROADCAST
|
|
|
|
|
bool
|
|
|
|
|
|
2012-05-18 15:59:57 +08:00
|
|
|
# Clockevents broadcasting infrastructure
|
|
|
|
|
config GENERIC_CLOCKEVENTS_BROADCAST
|
|
|
|
|
bool
|
|
|
|
|
depends on GENERIC_CLOCKEVENTS
|
|
|
|
|
|
2012-05-22 05:16:18 +08:00
|
|
|
# Automatically adjust the min. reprogramming time for
|
|
|
|
|
# clock event device
|
|
|
|
|
config GENERIC_CLOCKEVENTS_MIN_ADJUST
|
|
|
|
|
bool
|
|
|
|
|
|
2012-05-18 15:59:57 +08:00
|
|
|
# Generic update of CMOS clock
|
|
|
|
|
config GENERIC_CMOS_UPDATE
|
|
|
|
|
bool
|
2012-05-22 05:16:18 +08:00
|
|
|
|
|
|
|
|
if GENERIC_CLOCKEVENTS
|
|
|
|
|
menu "Timers subsystem"
|
|
|
|
|
|
2011-08-11 05:21:01 +08:00
|
|
|
# Core internal switch. Selected by NO_HZ_COMMON / HIGH_RES_TIMERS. This is
|
2012-05-22 05:16:18 +08:00
|
|
|
# only related to the tick functionality. Oneshot clockevent devices
|
|
|
|
|
# are supported independ of this.
|
|
|
|
|
config TICK_ONESHOT
|
|
|
|
|
bool
|
|
|
|
|
|
2011-08-11 05:21:01 +08:00
|
|
|
config NO_HZ_COMMON
|
|
|
|
|
bool
|
|
|
|
|
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
|
|
|
|
|
select TICK_ONESHOT
|
|
|
|
|
|
2011-08-11 05:21:01 +08:00
|
|
|
choice
|
|
|
|
|
prompt "Timer tick handling"
|
|
|
|
|
default NO_HZ_IDLE if NO_HZ
|
|
|
|
|
|
2013-04-13 22:53:35 +08:00
|
|
|
config HZ_PERIODIC
|
2011-08-11 05:21:01 +08:00
|
|
|
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 NO_HZ_IDLE
|
|
|
|
|
bool "Idle dynticks system (tickless idle)"
|
2012-05-22 05:16:18 +08:00
|
|
|
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
|
2011-08-11 05:21:01 +08:00
|
|
|
select NO_HZ_COMMON
|
2012-05-22 05:16:18 +08:00
|
|
|
help
|
2011-08-11 05:21:01 +08:00
|
|
|
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.
|
2012-05-22 05:16:18 +08:00
|
|
|
|
2013-04-12 22:45:34 +08:00
|
|
|
config NO_HZ_FULL
|
2013-04-13 23:04:04 +08:00
|
|
|
bool "Full dynticks system (tickless)"
|
2011-08-11 05:21:01 +08:00
|
|
|
# NO_HZ_COMMON dependency
|
2011-08-11 05:21:01 +08:00
|
|
|
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
|
2013-04-13 23:04:04 +08:00
|
|
|
# We need at least one periodic CPU for timekeeping
|
|
|
|
|
depends on SMP
|
|
|
|
|
depends on HAVE_CONTEXT_TRACKING
|
2013-04-26 21:16:31 +08:00
|
|
|
# VIRT_CPU_ACCOUNTING_GEN dependency
|
2013-09-17 06:28:21 +08:00
|
|
|
depends on HAVE_VIRT_CPU_ACCOUNTING_GEN
|
2011-08-11 05:21:01 +08:00
|
|
|
select NO_HZ_COMMON
|
2011-08-11 05:21:01 +08:00
|
|
|
select RCU_NOCB_CPU
|
2013-04-26 21:16:31 +08:00
|
|
|
select VIRT_CPU_ACCOUNTING_GEN
|
2013-04-18 06:15:40 +08:00
|
|
|
select IRQ_WORK
|
2011-08-11 05:21:01 +08:00
|
|
|
help
|
|
|
|
|
Adaptively try to shutdown the tick whenever possible, even when
|
2012-12-19 00:32:19 +08:00
|
|
|
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.
|
|
|
|
|
|
2013-04-12 22:45:34 +08:00
|
|
|
You need to fill up the nohz_full boot parameter with the
|
2012-12-19 00:32:19 +08:00
|
|
|
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.
|
|
|
|
|
|
2011-08-11 05:21:01 +08:00
|
|
|
endchoice
|
|
|
|
|
|
2013-03-27 08:17:22 +08:00
|
|
|
config NO_HZ_FULL_ALL
|
2014-02-07 02:36:21 +08:00
|
|
|
bool "Full dynticks system on all CPUs by default (except CPU 0)"
|
2013-03-27 08:17:22 +08:00
|
|
|
depends on NO_HZ_FULL
|
|
|
|
|
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.
|
|
|
|
|
|
2013-06-22 02:08:45 +08:00
|
|
|
config NO_HZ_FULL_SYSIDLE
|
|
|
|
|
bool "Detect full-system idle state for full dynticks system"
|
|
|
|
|
depends on NO_HZ_FULL
|
|
|
|
|
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.
|
|
|
|
|
|
2013-06-22 07:37:22 +08:00
|
|
|
config NO_HZ_FULL_SYSIDLE_SMALL
|
|
|
|
|
int "Number of CPUs above which large-system approach is used"
|
|
|
|
|
depends on NO_HZ_FULL_SYSIDLE
|
|
|
|
|
range 1 NR_CPUS
|
|
|
|
|
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 NO_HZ_FULL_SYSIDLE, (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 NO_HZ_FULL
|
|
|
|
|
entirely, given that NO_HZ_FULL 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.
|
|
|
|
|
|
2013-04-12 22:40:12 +08:00
|
|
|
config NO_HZ
|
|
|
|
|
bool "Old Idle dynticks config"
|
|
|
|
|
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
|
|
|
|
|
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.
|
|
|
|
|
|
2012-05-22 05:16:18 +08:00
|
|
|
config HIGH_RES_TIMERS
|
|
|
|
|
bool "High Resolution Timer Support"
|
|
|
|
|
depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
|
|
|
|
|
select TICK_ONESHOT
|
|
|
|
|
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
|
