Messages in this thread | | | Date | Thu, 19 Jan 2006 13:50:05 -0800 | From | George Anzinger <> | Subject | Re: [PATCH] Clean up of hrtimer code. |
| |
Thomas Gleixner wrote:
>George, > >On Thu, 2006-01-19 at 12:53 -0800, George Anzinger wrote: > > >>>The assumption that the CLOCK_REALTIME/MONOTONIC relationship is valid >>>for all additional clocks is not correct. >>> >>> >>Well, it is until it isn't. There really does need to be a paring of some >>sort to sort out the ABS flag. >> >> > >How is this applicable to some additional non posix clocks ? It applies >to CLOCK_MONOTONIC and CLOCK_REALTIME, but nothing speaks against >implementing CLOCK_WHATEVER with a totally different behaviour vs. the >ABS_TIME flag. Am I missing something ? > > > How ever it is done the selection of a base depends on the mode and the clock. I suggested mapping this via odd/ even, but, I think what is needed is some way to code this into hrtimer.c in a reasonable way. Your choice, really.
-- George Anzinger george@wildturkeyranch.net HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |