Lines Matching refs:event

17 Note: the paper and the slides are talking about "clock event source", while we
18 switched to the name "clock event devices" in meantime.
24 - clock event management
66 clock event management
70 value, clock event devices are used to schedule the next event
71 interrupt(s). The next event is currently defined to be periodic, with its
72 period defined at compile time. The setup and selection of the event device
73 for various event driven functionalities is hardwired into the architecture
76 event interrupt devices other than those already built into the
82 solution to manage clock event devices and their usage for the various clock
83 event driven kernel functionalities. The goal of the clock event subsystem is
84 to minimize the clock event related architecture dependent code to the pure
86 clock event devices. It also minimizes the duplicated code across the
90 Clock event devices are registered either by the architecture dependent boot
91 code or at module insertion time. Each clock event device fills a data
93 clock event management decides, by using the specified property parameters, the
94 set of system functions a clock event device will be used to support. This
95 includes the distinction of per-CPU and per-system global event devices.
97 System-level global event devices are used for the Linux periodic tick. Per-CPU
98 event devices are used to provide local CPU functionality such as process
102 event device:
106       - cpu local next event interrupt (non periodic mode)
108 The clock event device delegates the selection of those timer interrupt related
113 clock event devices and the assignment of timer interrupt related functionality
116 The clock event layer API is rather small. Aside from the clock event device
117 registration interface it provides functions to schedule the next event
118 interrupt, clock event device notification service and support for suspend and
129 to the clock event device and timer interrupt code. After the conversion the
143 useful function. The initialization of the clock event device framework, the
145 appropriate clock sources and clock event devices have to be registered before
148 clock source and the clock event device layers provide notification functions
150 the usability of the registered clock sources and clock event devices before
156 global clock event devices. The support of such hardware would involve IPI
164 whether the event device has to be reprogrammed when a timer is added. The
167 clock event devices for the per-CPU timer bases, but currently only one
168 reprogrammable clock event device per-CPU is utilized.
170 When the timer interrupt happens, the next event interrupt handler is called
171 from the clock event distribution code and moves expired timers from the
174 execute callback functions directly from the next event interrupt handler. This
183 switched off. This disables the per system global periodic clock event device -
187 function is executed in the next event interrupt context and updates jiffies
190 This allows to use a single clock event device to schedule high resolution
216 evaluates the next scheduled timer event (from both hrtimers and the timer
217 wheel) and in case that the next event is further away than the next tick it
218 reprograms the sched_tick to this future event, to allow longer idle sleeps
223 nearest event in the previous call to hrtimer_stop_sched_tick.