admin-guide/pm/cpuidle.rst

33 CPU idle time management operates on CPUs as seen by the *CPU scheduler* (that
84 Tasks are the CPU scheduler's representation of work.  Each task consists of a
87 processor every time the task's code is run by a CPU.  The CPU scheduler
93 events to occur or similar).  When a task becomes runnable, the CPU scheduler
164 configuration of the kernel and in particular on whether or not the scheduler
188 Idle CPUs and The Scheduler Tick
191 The scheduler tick is a timer that triggers periodically in order to implement
192 the time sharing strategy of the CPU scheduler.  Of course, if there are
199 may not want to give the CPU away voluntarily, however, and the scheduler tick
203 The scheduler tick is problematic from the CPU idle time management perspective,
214 "idle" one.  In other words, from the CPU scheduler perspective, the only user
218 the scheduler tick entirely on idle CPUs in principle, even though that may not
221 Whether or not it makes sense to stop the scheduler tick in the idle loop
242 or not to stop the scheduler tick belongs to it.  Still, if the tick has been
246 The kernel can be configured to disable stopping the scheduler tick in the idle
250 scheduler tick is disabled, the governor's decisions regarding it are simply
253 The systems that run kernels configured to allow the scheduler tick to be
273 that the scheduler tick will be stopped.  That time, referred to as the *sleep
331 if it has not decided to `stop the scheduler tick <idle-cpus-and-tick_>`_.  That
358 values less than the current time till the closest timer (with the scheduler
363 assumption that the scheduler tick will be stopped (that also is the upper bound
416 it has not decided to `stop the scheduler tick <idle-cpus-and-tick_>`_.  That