> Hmmm. Thats likely part to blame for the lost-ticks code not working. I
> believe tick_usec is calculated USER_HZ rather then HZ, so you'll be off
> by an order of magnitude. I ran into the exact same problem.
Unlikely. On my systems, the offset values are off by three orders of
magnitude, and are always negative. There's a more basic error
somewhere before that test.
The actual impact of lost jiffies is pretty low, though. I've beaten
vigorously on my systems with the time patch, and they don't lose timer
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/