public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Shishkin <virtuoso@slind.org>,
	lkml@vger.kernel.org, "Kirill A. Shutemov" <kirill@shutemov.name>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Stultz <johnstul@us.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	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>,
	Kay Sievers <kay.sievers@vrfy.org>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFCv2] notify userspace about time changes
Date: Wed, 18 Aug 2010 17:50:17 -0600	[thread overview]
Message-ID: <4C6C71B9.6090606@genband.com> (raw)
In-Reply-To: <20100818155702.bc62b2a6.akpm@linux-foundation.org>

On 08/18/2010 04:57 PM, Andrew Morton wrote:

> The requirements sound a bit fluffy to me.
> 
> Any time-displaying application will find out the new time next time
> it reads the time.  So afaict this is only really useful for clock
> applets which display once per minute, so they will show the new time
> promptly after the time was altered, yes?  Is that really worth adding
> new code for?

There are other users of this functionality.  We have an emulator
running on top of linux which in turn runs code originally intended for
another OS.  It cares about walltime, so it wants to know ASAP if the
linux system time changes.

We've actually been carrying an internal patch doing something like this
for years now...never pushed it to mainline since we didn't think anyone
else would be interested.

Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com

  parent reply	other threads:[~2010-08-18 23:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 13:55 [PATCH] [RFCv2] notify userspace about time changes Alexander Shishkin
2010-08-18 14:26 ` Greg KH
2010-08-18 22:57 ` Andrew Morton
2010-08-18 23:43   ` H. Peter Anvin
2010-08-18 23:53     ` Andrew Morton
2010-08-19  4:09       ` Greg KH
2010-08-19  4:39         ` Andrew Morton
2010-08-19  8:21         ` Alexander Shishkin
2010-08-19  8:36         ` Kirill A. Shutemov
2010-08-19  8:39           ` Kay Sievers
2010-08-19 15:31           ` Greg KH
2010-08-20  8:37             ` Kirill A. Shutemov
2010-08-20 15:33               ` Greg KH
2010-08-20 15:38                 ` Alexander Shishkin
2010-08-19  9:50       ` Peter Zijlstra
2010-08-19 10:53         ` Kay Sievers
2010-08-19 11:14         ` Alexander Shishkin
2010-08-18 23:50   ` Chris Friesen [this message]
2010-08-18 23:09 ` 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=4C6C71B9.6090606@genband.com \
    --to=chris.friesen@genband.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=johnstul@us.ibm.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