Lines Matching +full:hardware +full:- +full:driven

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
50 specific portion is reduced to the low level hardware details of the clock
52 decision. The low level code provides hardware setup and readout routines and
70 ----------------------
76 for various event driven functionalities is hardwired into the architecture
81 to touch all the architecture-specific implementations in order to provide new
86 event driven kernel functionalities. The goal of the clock event subsystem is
88 hardware related handling and to allow easy addition and utilization of new
91 service handler, which is almost inherently hardware dependent.
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)
115 from the hardware level handler. This removes a lot of duplicated code from the
143 -----------------------------------
153 which inform hrtimers about availability of new hardware. hrtimers validates
157 necessary hardware support.
160 global clock event devices. The support of such hardware would involve IPI
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.
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
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
209 -------------
215 - hrtimer_stop_sched_tick
216 - hrtimer_restart_sched_tick
217 - hrtimer_update_jiffies