Lines Matching +full:local +full:- +full:timer +full:- +full:stop
8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
37 The main differences to the timer wheel, which holds the armed timer_list type
40 - time ordered enqueueing into a rb-tree
41 - independent of ticks (the processing is based on nanoseconds)
45 -------------------------------------
48 code out of the architecture-specific areas into a generic management
70 ----------------------
81 to touch all the architecture-specific implementations in order to provide new
95 structure with clock-specific property parameters and callback functions. The
98 includes the distinction of per-CPU and per-system global event devices.
100 System-level global event devices are used for the Linux periodic tick. Per-CPU
101 event devices are used to provide local CPU functionality such as process
107 - system global periodic tick (jiffies update)
108 - cpu local update_process_times
109 - cpu local profiling
110 - cpu local next event interrupt (non periodic mode)
112 The clock event device delegates the selection of those timer interrupt related
116 architecture specific timer interrupt handlers and hands the control over the
117 clock event devices and the assignment of timer interrupt related functionality
133 to the clock event device and timer interrupt code. After the conversion the
142 high resolution timer functionality
143 -----------------------------------
145 During system boot it is not possible to use the high resolution timer
159 The high resolution timer code does not support SMP machines which have only
163 dynamic ticks on i386 SMP systems which stop the local APIC in C3 power
168 whether the event device has to be reprogrammed when a timer is added. The
169 decision is made per timer base and synchronized across per-cpu timer bases in
170 a support function. The design allows the system to utilize separate per-CPU
171 clock event devices for the per-CPU timer bases, but currently only one
172 reprogrammable clock event device per-CPU is utilized.
174 When the timer interrupt happens, the next event interrupt handler is called
176 red-black tree to a separate double linked list and invokes the softirq
182 context is the avoidance of up to two context switches - from the interrupted
184 timer.
187 switched off. This disables the per system global periodic clock event device -
190 The periodic tick functionality is provided by an per-cpu hrtimer. The callback
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
201 resolution timer signals which are used by itimer and POSIX interval
209 -------------
215 - hrtimer_stop_sched_tick
216 - hrtimer_restart_sched_tick
217 - hrtimer_update_jiffies
220 evaluates the next scheduled timer event (from both hrtimers and the timer
226 new timer whose expiry time is before the time which was identified as the