Re: Use of absolute timeouts for oneshot timers

2007-03-11 Thread Thomas Gleixner
On Sat, 2007-03-10 at 16:42 -0800, Jeremy Fitzhardinge wrote: > Thomas Gleixner wrote: > > It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute > > time, which is read back from the clocksource, even if we use a relative > > value for real hardware clock event devices to program

Re: Use of absolute timeouts for oneshot timers

2007-03-11 Thread Thomas Gleixner
On Sat, 2007-03-10 at 16:42 -0800, Jeremy Fitzhardinge wrote: Thomas Gleixner wrote: It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute time, which is read back from the clocksource, even if we use a relative value for real hardware clock event devices to program the next

Re: Use of absolute timeouts for oneshot timers

2007-03-10 Thread Jeremy Fitzhardinge
Thomas Gleixner wrote: > It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute > time, which is read back from the clocksource, even if we use a relative > value for real hardware clock event devices to program the next event. > We calculate the delta between the absolute event and

Re: Use of absolute timeouts for oneshot timers

2007-03-10 Thread Jeremy Fitzhardinge
Thomas Gleixner wrote: > The clocksource is not used until the clocksource is installed. Also the > periodic mode during boot, when the clock event device supports periodic > mode, is not reading the time. It relies on the clock event device > getting it straight. Yes. This could be one source

Re: Use of absolute timeouts for oneshot timers

2007-03-10 Thread Thomas Gleixner
On Sat, 2007-03-10 at 14:52 -0800, Jeremy Fitzhardinge wrote: > When booting under Xen, you'll get this if you're using both the xen > clocksource and clockevent drivers. However, it seems that during boot > on a NO_HZ HIGHRES_TIMERS system, the kernel does not use the Xen > clocksource until it

Re: Use of absolute timeouts for oneshot timers

2007-03-10 Thread Thomas Gleixner
On Sat, 2007-03-10 at 14:52 -0800, Jeremy Fitzhardinge wrote: When booting under Xen, you'll get this if you're using both the xen clocksource and clockevent drivers. However, it seems that during boot on a NO_HZ HIGHRES_TIMERS system, the kernel does not use the Xen clocksource until it

Re: Use of absolute timeouts for oneshot timers

2007-03-10 Thread Jeremy Fitzhardinge
Thomas Gleixner wrote: The clocksource is not used until the clocksource is installed. Also the periodic mode during boot, when the clock event device supports periodic mode, is not reading the time. It relies on the clock event device getting it straight. Yes. This could be one source of

Re: Use of absolute timeouts for oneshot timers

2007-03-10 Thread Jeremy Fitzhardinge
Thomas Gleixner wrote: It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute time, which is read back from the clocksource, even if we use a relative value for real hardware clock event devices to program the next event. We calculate the delta between the absolute event and