Re: [PATCH_TAKE_2] now < last_tick problem

Ian Wienand
2003-10-14T05:53:15Z

On Mon, Oct 13, 2003 at 10:23:39PM -0700, David Mosberger wrote:
> consistency-check. May want to add a comment about that, though.

A few messages up I added something like

+ * Return the number of nano-seconds that elapsed since the last
+ * update to jiffy. It is quite possible that the timer interrupt
+ * will interrupt this and result in a race for any of jiffies,
+ * wall_jiffies or itm_next. Thus, the xtime_lock must be at least
+ * read-locked when calling this routine.

although read-locked should probably be 'read synchronised' or
something to avoid confusion.

-i