From: john stultz <johnstul@us.ibm.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alexander Shishkin <virtuoso@slind.org>,
gregkh@suse.de, lkml@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Thomas Gleixner <tglx@linutronix.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jon Hunter <jon-hunter@ti.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>, Avi Kivity <avi@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, John Kacur <jkacur@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] notify userspace about time changes
Date: Thu, 05 Aug 2010 15:30:30 -0700 [thread overview]
Message-ID: <1281047430.3405.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1281047390.3405.22.camel@localhost.localdomain>
On Thu, 2010-08-05 at 15:29 -0700, john stultz wrote:
> On Fri, 2010-08-06 at 00:17 +0200, Kay Sievers wrote:
> > On Thu, Aug 5, 2010 at 23:11, john stultz <johnstul@us.ibm.com> wrote:
> > > On Thu, 2010-08-05 at 15:33 +0300, Alexander Shishkin wrote:
> > >> On 4 August 2010 18:58, john stultz <johnstul@us.ibm.com> wrote:
> > >> > Is there a actual use case that you need this for? I don't really have
> > >> > an issue with the code I just really want to make sure the feature would
> > >> > be useful enough to justify the API and code maintenance going forward.
> >
> > Basically everything that schedules an action based on an absolute
> > time specification, like at 3pm today, and not in 3 hours from now,
> > needs to track such system time changes. Otherwise it has to do
> > nonsense like cron does, to wake up every minute to check the current
> > time.
>
> time_create(CLOCK_REALTIME,...) creates absolute (not relative) timers
Sorry, *timer_create*.
thanks
-john
next prev parent reply other threads:[~2010-08-05 22:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 12:48 [PATCH] [RFC] notify userspace about time changes Alexander Shishkin
2010-08-04 12:54 ` Bastien ROUCARIES
2010-08-04 15:49 ` Alexander Shishkin
2010-08-04 15:32 ` Kirill A. Shutemov
2010-08-04 15:46 ` Alexander Shishkin
2010-08-05 10:05 ` Kirill A. Shutemov
2010-08-04 15:58 ` john stultz
2010-08-04 18:48 ` Chris Friesen
2010-08-05 0:52 ` john stultz
2010-08-05 12:39 ` Alexander Shishkin
2010-08-05 14:10 ` Chris Friesen
2010-08-05 12:33 ` Alexander Shishkin
2010-08-05 21:11 ` john stultz
2010-08-05 21:38 ` Greg KH
2010-08-05 22:22 ` Kay Sievers
2010-08-05 22:34 ` H. Peter Anvin
2010-08-05 22:39 ` Kay Sievers
2010-08-05 22:43 ` H. Peter Anvin
2010-08-05 22:38 ` Greg KH
2010-08-06 7:21 ` Alexander Shishkin
2010-08-06 23:44 ` Greg KH
2010-08-06 7:11 ` Alexander Shishkin
2010-08-06 7:43 ` Bastien ROUCARIES
2010-08-05 22:17 ` Kay Sievers
2010-08-05 22:29 ` john stultz
2010-08-05 22:30 ` john stultz [this message]
2010-08-05 23:50 ` Kay Sievers
2010-08-06 0:16 ` john stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1281047430.3405.23.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=dhowells@redhat.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=jkacur@redhat.com \
--cc=jon-hunter@ti.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=virtuoso@slind.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox