[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=R3k+hijuvomR4ABKd9ruhVRV39MhW4Zb4=Dh8@mail.gmail.com>
Date: Thu, 19 Aug 2010 12:53:31 +0200
From: Kay Sievers <kay.sievers@...y.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Alexander Shishkin <virtuoso@...nd.org>, lkml@...r.kernel.org,
"Kirill A. Shutemov" <kirill@...temov.name>,
Thomas Gleixner <tglx@...utronix.de>,
John Stultz <johnstul@...ibm.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Jon Hunter <jon-hunter@...com>, Ingo Molnar <mingo@...e.hu>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
David Howells <dhowells@...hat.com>,
Avi Kivity <avi@...hat.com>, John Kacur <jkacur@...hat.com>,
Chris Friesen <chris.friesen@...band.com>,
Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [RFCv2] notify userspace about time changes
On Thu, Aug 19, 2010 at 11:50, Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, 2010-08-18 at 16:53 -0700, Andrew Morton wrote:
>>
>> Such applications might be better served via a wake-me-at-this-time
>> syscall instead of a sleep-me-for-this-long syscall. Although such a
>> thing is less general.
>>
> We have timer_create(.clockid = CLOCK_REALTIME) for such things, no?
Not for repeating events like cron needs.
Say we want to wakeup at 3pm, now it's 4pm, so we schedule it in 23
hours. Now the system time changes to 2pm, and we would expect to
wakeup in one hour, but we take 25.
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists