Lines Matching refs:and

1 High resolution timers and dynamic ticks design notes
5 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
14 design of the Linux time(r) system before hrtimers and other building blocks
17 Note: the paper and the slides are talking about "clock event source", while we
23 - timeofday and clock source management
42 timeofday and clock source management
49 sources, which are registered in the framework and selected on a quality based
50 decision. The low level code provides hardware setup and readout routines and
60 The paper "We Are Not Getting Any Younger: A New Approach to Time and
72 period defined at compile time. The setup and selection of the event device
74 dependent code. This results in duplicated code across all architectures and
82 solution to manage clock event devices and their usage for the various clock
85 hardware related handling and to allow easy addition and utilization of new
92 structure with clock-specific property parameters and callback functions. The
95 includes the distinction of per-CPU and per-system global event devices.
99 accounting, profiling, and high resolution timers.
112 architecture specific timer interrupt handlers and hands the control over the
113 clock event devices and the assignment of timer interrupt related functionality
118 interrupt, clock event device notification service and support for suspend and
124 increase of flexibility and the avoidance of duplicated code across
128 utilize the high resolution and dynamic tick functionalities without any change
129 to the clock event device and timer interrupt code. After the conversion the
130 enabling of high resolution timers and dynamic ticks is simply provided by
131 adding the kernel/time/Kconfig file to the architecture specific Kconfig and
133 added to the idle function and the Kconfig file)
142 functionality, while making it possible would be difficult and would serve no
144 clock source framework (GTOD) and hrtimers itself has to be done and
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
158 benefit. This is the reason why we currently disable high resolution and
165 decision is made per timer base and synchronized across per-cpu timer bases in
171 from the clock event distribution code and moves expired timers from the
172 red-black tree to a separate double linked list and invokes the softirq
179 context to the softirq and to the task which is woken up by the expired
187 function is executed in the next event interrupt context and updates jiffies
188 and calls update_process_times and profiling. The implementation of the hrtimer
191 timer and periodic events (jiffies tick, profiling, process accounting) on UP
192 systems. This has been proved to work with the PIT on i386 and the Incrementer
195 The softirq for running the hrtimer queues and executing the callbacks has been
197 resolution timer signals which are used by itimer and POSIX interval
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
230 in the idle period to make sure that jiffies are up to date and the interrupt
234 userspace via /proc/stats and can be made available for enhanced power
239 frequency profiling, and a complete removal of jiffies in the future.
243 extended to x86_64 and ARM already. Initial (work in progress) support is also
244 available for MIPS and PowerPC.