Re: [BUG, RFC] do_gettimeofday going backwards

From: David Mosberger <>
Date: 2003-10-15 11:17:32
>>>>> On Tue, 30 Sep 2003 18:00:03 -0700 (PDT), John Hawkes <> said:

  John> What's wrong?  Suppose that the timer interrupt occurs every
  John> 1000 usecs.  Suppose timer_bh executes at time RTC==t0, and
  John> that at that point we have xtime.tv_sec==0 and tv_usec==0.
  John> The SN2 hook remembers this t0 timestamp.  A subsequent call
  John> to do_gettimeofday() computes the offset (tCurrent - t0) and
  John> adds this to the xtime.tv_* value pair.  Thus, based upon this
  John> initial xtime value pair, do_gettimeofday() returns a nicely
  John> ascending TOD value.

  John> Now suppose the next timer interrupt occurs, but the timer_bh
  John> gets delayed by 100 useconds.  Just prior to timer_bh
  John> executing, a do_gettimeofday() computes an offset of 1099
  John> usecs, so it returns a TOD of tv_usec==(0+1099).  Then
  John> timer_bh executes and updates tv_usec==1000 and timestamps
  John> that at RTC time t1==(t0+1100).  Just *after* the timer_bh
  John> executes, a do_gettimeofday() computes an offset of zero, and
  John> thus computes tv_usec==(1000+0).  The TOD tv_usec just went
  John> backwards, from 1099 to 1000.

Then your time-interpolator is broken.  As I have expained on previous
occasions (in particular in a mail to Jes), last_nsec_offset must not
be _cleared_ on a timer-tick.  Instead, it needs to be decremented by
the timer tick period.  So in your case, last_nsec_offset would
decrease from 1099000 to 99000.

Somehow, I have a feeling you're looking at 2.4.  If so, please take a
look at the time-interpolator code in 2.6 (see
CONFIG_TIME_INTERPOLATION near the end of include/linux/timex.h).

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Tue Oct 14 21:17:52 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:19 EST