Searched full:tick (Results 1 – 25 of 49) sorted by relevance
12
| /Documentation/timers/ |
| D | highres.rst | 100 System-level global event devices are used for the Linux periodic tick. Per-CPU
107 - system global periodic tick (jiffies update)
132 utilize the high resolution and dynamic tick functionalities without any change
136 adding the dynamic tick specific calls to the idle routine (a total of 3 lines
186 Once a system has switched to high resolution mode, the periodic tick is
190 The periodic tick functionality is provided by an per-cpu hrtimer. The callback
193 based periodic tick is designed to be extended with dynamic tick functionality.
195 timer and periodic events (jiffies tick, profiling, process accounting) on UP
200 separated from the tick bound timer softirq to allow accurate delivery of high
211 Dynamic ticks are the logical consequence of the hrtimer based periodic tick
[all …]
|
| D | no_hz.rst | 128 adaptive-tick CPUs: At least one non-adaptive-tick CPU must remain
130 calls like gettimeofday() returns accurate values on adaptive-tick CPUs.
144 Just as with dyntick-idle mode, the benefits of adaptive-tick mode do
156 3. POSIX CPU timers prevent CPUs from entering adaptive-tick mode.
162 all of them over time. Adaptive-tick mode may prevent this
165 entering adaptive-tick mode.
167 5. Scheduler statistics for adaptive-tick CPUs may be computed
168 slightly differently than those for non-adaptive-tick CPUs.
181 enter either dyntick-idle mode or adaptive-tick mode, the most
193 or adaptive-tick mode. That said, note that it is up to userspace to
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 165 tick can be `stopped by the idle loop <idle-cpus-and-tick_>`_. Available
186 .. _idle-cpus-and-tick:
188 Idle CPUs and The Scheduler Tick
191 The scheduler tick is a timer that triggers periodically in order to implement
199 may not want to give the CPU away voluntarily, however, and the scheduler tick
201 tick, but it is the primary reason for using it.
203 The scheduler tick is problematic from the CPU idle time management perspective,
205 configuration, the length of the tick period is between 1 ms and 10 ms).
206 Thus, if the tick is allowed to trigger on idle CPUs, it will not make sense
208 the tick period length. Moreover, in that case the idle duration of any CPU
[all …]
|
| D | suspend-flows.rst | 99 4. Freezing the scheduler tick and suspending timekeeping.
103 "freezes" its own scheduler tick so that the timer events associated with
104 the tick do not occur until the CPU is woken up by another interrupt source.
126 1. Resuming timekeeping and unfreezing the scheduler tick.
131 by another CPU that woke up earlier) and the scheduler tick on that CPU is
|
| /Documentation/devicetree/bindings/timer/ |
| D | faraday,fttmr010.txt | 22 - clocks : a clock to provide the tick rate for "faraday,fttmr010"
23 - clock-names : should be "EXTCLK" and "PCLK" for the external tick timer
|
| D | arm,arch_timer_mmio.yaml | 55 arm,no-tick-in-suspend:
57 description: The main counter does not tick when the system is in
|
| D | ralink,cevt-systick.yaml | 7 title: System tick counter present in Ralink family SoCs
|
| D | arm,arch_timer.yaml | 98 arm,no-tick-in-suspend:
100 description: The main counter does not tick when the system is in
|
| /Documentation/features/time/arch-tick-broadcast/ |
| D | arch-support.txt | 2 # Feature name: arch-tick-broadcast
|
| /Documentation/devicetree/bindings/rtc/ |
| D | nxp,lpc1788-rtc.yaml | 11 together with periodic tick and alarm interrupt support.
|
| D | s3c-rtc.yaml | 50 is the rtc tick interrupt. The number of cells representing a interrupt
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | cirrus,clps711x-intc.txt | 23 11: TINT 64Hz tick
|
| /Documentation/devicetree/bindings/misc/ |
| D | qemu,vcpu-stall-detector.yaml | 28 to decrement its internal counter register on each tick.
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | alphascale,asm9260-wdt.yaml | 24 - description: source clock, used for tick counter
|
| D | realtek,otto-wdt.yaml | 15 minimum duration of each phase is one tick. Each phase can trigger an
|
| D | ti,rti-wdt.yaml | 63 * select the source clock for the watchdog, forcing it to tick with
|
| D | snps,dw-wdt.yaml | 65 the timer restart. The counter decrementing happens each tick of the
|
| /Documentation/sound/ |
| D | utimers.rst | 66 /* Timer is going to tick (presumably) every 1000000 ns */
122 the timer is going to tick every time a new period of frames is ready.
|
| /Documentation/driver-api/hte/ |
| D | tegra-hte.rst | 12 converts clock tick rate to nanoseconds before storing it as timestamp value.
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 94 down the seconds to the full seconds of the last timer tick
122 The time returned here corresponds to the last timer tick, which
|
| D | entry.rst | 168 return true, handles NOHZ tick state and interrupt time accounting. This
173 count update and eventually handles soft interrupts and NOHZ tick state.
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 125 the scheduler tick before asking the processor to enter the selected
129 stopping the scheduler tick on the given CPU (if the tick has been
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 148 as System/Tick timers for the OS running on the remote
156 external tick wakeup, and to support Power Management
|
| /Documentation/driver-api/thermal/ |
| D | power_allocator.rst | 267 periodic tick. If you have a driver that calls
272 faster than the normal thermal framework tick (due to interrupts for
|
| /Documentation/scheduler/ |
| D | sched-design-CFS.rst | 83 schedules (or a scheduler tick happens) the task's CPU usage is "accounted
206 This function is mostly called from time tick functions; it might lead to
|
12