Lines Matching +full:per +full:- +full:device

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 ----------------------
75 period defined at compile time. The setup and selection of the event device
81 to touch all the architecture-specific implementations in order to provide new
94 code or at module insertion time. Each clock event device fills a data
95 structure with clock-specific property parameters and callback functions. The
97 set of system functions a clock event device will be used to support. This
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
105 event device:
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
114 a function pointer in the device description structure, which has to be called
120 The clock event layer API is rather small. Aside from the clock event device
122 interrupt, clock event device notification service and support for suspend and
133 to the clock event device and timer interrupt code. After the conversion the
143 -----------------------------------
147 useful function. The initialization of the clock event device framework, the
152 clock source and the clock event device layers provide notification functions
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.
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
194 This allows to use a single clock event device to schedule high resolution
209 -------------
215 - hrtimer_stop_sched_tick
216 - hrtimer_restart_sched_tick
217 - hrtimer_update_jiffies