Re: [PATCH_TAKE_2] now < last_tick problem

From: Ian Wienand <>
Date: 2003-10-14 15:53:15
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.

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 01:55:55 2003

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