[lkml]   [2005]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Incorrect CLOCK_TICK_RATE in 2.6 kernel
john stultz wrote:
> On Wed, 2005-08-24 at 17:24 -0700, George Anzinger wrote:
>>CLOCK_TICK_RATE is used by the kernel to compute LATCH, TICK_NSEC and
>>tick_nsec. This latter is used to update xtime each tick. TICK_NSEC is
>>then used to compute (at compile time) the conversion constants needed
>>to convert to/from jiffies from/to timespec and timeval (and others).
>>The problem is that, if the timer being used is either Cyclone or HPET,
>>the wrong CLOCK_TICK_RATE is used.
> Err, the Cyclone does not generate interrupts. So this issue does not
> affect those systems.
> As for the HPET, it sets its own interrupt frequency based off of
> KERNEL_TICK_USEC (which you're right, isn't quite what is used in the
> jiffies conversions). Would it be easier to just adjust that value to

If you want to take that approach you would want the HPET to interrupt
every TICK_NSEC nanoseconds, that being what xtime is pushed by each tick.

George Anzinger
HRT (High-res-timers):
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-08-25 03:33    [W:0.028 / U:6.224 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site