On Mon, 2007-09-24 at 13:22 -0700, Davide Libenzi wrote: > I think that advancing the timer against the timer's current "now" can > be a pretty common usage, so, w/out exposing hrtimer's internals, we add > a new hrtimer_forward_now() function. > > > > Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
Reviewed-and-Acked-by: Thomas Gleixner <[EMAIL PROTECTED]> > > - Davide > > > --- > include/linux/hrtimer.h | 7 +++++++ > 1 file changed, 7 insertions(+) > > Index: linux-2.6.mod/include/linux/hrtimer.h > =================================================================== > --- linux-2.6.mod.orig/include/linux/hrtimer.h 2007-09-24 > 12:27:20.000000000 -0700 > +++ linux-2.6.mod/include/linux/hrtimer.h 2007-09-24 12:29:39.000000000 > -0700 > @@ -298,6 +298,13 @@ > extern unsigned long > hrtimer_forward(struct hrtimer *timer, ktime_t now, ktime_t interval); > > +/* Forward a hrtimer so it expires after the hrtimer's current now */ > +static inline unsigned long hrtimer_forward_now(struct hrtimer *timer, > + ktime_t interval) > +{ > + return hrtimer_forward(timer, timer->base->get_time(), interval); > +} > + > /* Precise sleep: */ > extern long hrtimer_nanosleep(struct timespec *rqtp, > struct timespec __user *rmtp, > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/