![]() | |||||||||||||
Messages in this thread |
On 5/12/07, Thomas Gleixner <tglx@linutronix.de> wrote: > On Sat, 2007-05-12 at 22:13 +0200, Francis Moreau wrote: > > > Yes, it is correct. The generic timer code requests an event in the > > > future. It does not care, whether the hardware device can handle that or > > > not. So the clock event code limits the delta to the maximum delta the > > > device can handle. The interrupt fires and the generic timer code > > > reschedules the event with the remaining delta time. > > > > > > > Thanks again for explanations. Could you give me a pointer of this reschedules ? > > Well, it ends up in hrtimer_interrupt() and the code there finds out, > that the next timer is not due right now, so it simply requests the same > (absolute) time event again, which is processed by the clock events code > and eventually limited to the max delta of the device again. > OK, I'll give it a deeper look soon. Thanks for your great work ! -- Francis - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-05-13 05:55 [from the cache] ©2003-2008 | |||||||||||||