From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: For review: timer_settime.2 Date: Thu, 12 Feb 2009 14:54:24 +0100 Message-ID: <1234446864.10603.6.camel@laptop> References: <4990DE50.7090503@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4990DE50.7090503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Michael Kerrisk Cc: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Thomas Gleixner List-Id: linux-man@vger.kernel.org On Tue, 2009-02-10 at 14:54 +1300, Michael Kerrisk wrote: > If the value of the CLOCK_REALTIME clock is adjusted while an > absolute timer based on that clock is armed, then the expira- > tion of the timer will be appropriately adjusted. Adjustments > to the CLOCK_REALTIME clock have no effect on relative timers > based on that clock. I cannot find this to be true. >>From what I can make of the code, clock_settime() ends up calling do_sys_settimeofday() for CLOCK_REALTIME (and the other clocks). It is, however, not treating relative/abs timers any differently. Both get converted to an absolute expiration time when set. If POSIX mandates that we keep relative timers unchanged when we change the underlying clock, we'd have to iterate all pending timers and reset them. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html