Lines Matching full:and

2 High resolution timers and dynamic ticks design notes
6 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
15 design of the Linux time(r) system before hrtimers and other building blocks
18 Note: the paper and the slides are talking about "clock event source", while we
24 - timeofday and clock source management
44 timeofday and clock source management
51 sources, which are registered in the framework and selected on a quality based
52 decision. The low level code provides hardware setup and readout routines and
63 The paper "We Are Not Getting Any Younger: A New Approach to Time and
75 period defined at compile time. The setup and selection of the event device
77 dependent code. This results in duplicated code across all architectures and
85 solution to manage clock event devices and their usage for the various clock
88 hardware related handling and to allow easy addition and utilization of 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.
102 accounting, profiling, and high resolution timers.
116 architecture specific timer interrupt handlers and hands the control over the
117 clock event devices and the assignment of timer interrupt related functionality
122 interrupt, clock event device notification service and support for suspend and
128 increase of flexibility and the avoidance of duplicated code across
132 utilize the high resolution and dynamic tick functionalities without any change
133 to the clock event device and timer interrupt code. After the conversion the
134 enabling of high resolution timers and dynamic ticks is simply provided by
135 adding the kernel/time/Kconfig file to the architecture specific Kconfig and
137 added to the idle function and the Kconfig file)
146 functionality, while making it possible would be difficult and would serve no
148 clock source framework (GTOD) and hrtimers itself has to be done and
149 appropriate clock sources and clock event devices have to be registered before
152 clock source and the clock event device layers provide notification functions
154 the usability of the registered clock sources and clock event devices before
162 benefit. This is the reason why we currently disable high resolution and
169 decision is made per timer base and synchronized across per-cpu timer bases in
175 from the clock event distribution code and moves expired timers from the
176 red-black tree to a separate double linked list and invokes the softirq
183 context to the softirq and to the task which is woken up by the expired
191 function is executed in the next event interrupt context and updates jiffies
192 and calls update_process_times and profiling. The implementation of the hrtimer
195 timer and periodic events (jiffies tick, profiling, process accounting) on UP
196 systems. This has been proved to work with the PIT on i386 and the Incrementer
199 The softirq for running the hrtimer queues and executing the callbacks has been
201 resolution timer signals which are used by itimer and POSIX interval
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
234 in the idle period to make sure that jiffies are up to date and the interrupt
238 userspace via /proc/stat and can be made available for enhanced power
243 frequency profiling, and a complete removal of jiffies in the future.
247 extended to x86_64 and ARM already. Initial (work in progress) support is also
248 available for MIPS and PowerPC.