Lines Matching +full:next +full:- +full:mode

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 ---------------------------
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 ----------------------
73 value, clock event devices are used to schedule the next event
74 interrupt(s). The next event is currently defined to be periodic, with its
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
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)
121 registration interface it provides functions to schedule the next event
143 -----------------------------------
151 initialized, the system works in the usual low resolution periodic mode. The
155 switching to high resolution mode. This ensures also that a kernel which is
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
177 handler. An additional mode field in the hrtimer structure allows the system to
178 execute callback functions directly from the next event interrupt handler. This
182 context is the avoidance of up to two context switches - from the interrupted
186 Once a system has switched to high resolution mode, the periodic tick is
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
191 function is executed in the next event interrupt context and updates jiffies
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
221 wheel) and in case that the next event is further away than the next tick it
231 which is kept active until the next call to hrtimer_stop_sched_tick().