public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Shishkin <virtuoso@slind.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Greg KH <gregkh@suse.de>,
	Chris Friesen <chris.friesen@genband.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Thomas Gleixner <tglx@linutronix.de>,
	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>,
	John Kacur <jkacur@redhat.com>,
	Alexander Shishkin <virtuoso@slind.org>
Subject: Re: [PATCH 1/7] notify userspace about time changes
Date: Fri, 17 Sep 2010 14:08:03 +0300	[thread overview]
Message-ID: <20100917110803.GC10463@shisha.kicks-ass.net> (raw)
In-Reply-To: <AANLkTimGG4ocs5r18Fz8bt0v_V+7+HGdxeoze5PtO6G2@mail.gmail.com>

On Fri, Sep 17, 2010 at 12:22:36 +0200, Kay Sievers wrote:
> On Fri, Sep 17, 2010 at 12:33, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >> Certain userspace applications (like "clock" desktop applets or cron) might
> >> want to be notified when some other application changes the system time. It
> >> might also be important for an application to be able to distinguish between
> >> its own and somebody else's time changes.
> >
> > A program that cannot work out if it or someone else changed the time is
> > very very broken indeed !
> 
> Yeah, that seems a bit weird to me too.

Ok, I get it. Filtering has to go.

> > Clocks apps don't care because they check the actual time so notice it
> > shfited. Cron and anacron appear to contain the needed internal handling.
> 
> Cron wakes up every minute to check if the time has changed. We don't
> want such silly behavior, but there are no other options at the moment
> for scheduling re-occurring events.
> 
> > Anything sleeping until a time occurs maybe ? In which case its a lot
> > simpler and cleaner than events to provide a new itimer which wakes the
> > process when the wall time hits the time specified in the timer.
> 
> That seems not sufficient. The details should be in the changelog of the patch.

Yes, I did include your description of the problem in the 0/7, but
that doesn't seem sufficient. I really need to compile all the
usecases from previous threads and include them in 1/7 as well.

Regards,
--
Alex

  reply	other threads:[~2010-09-17 11:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 22:10 [PATCHv5 0/7] system time changes notification Alexander Shishkin
2010-09-16 22:10 ` [PATCH 1/7] notify userspace about time changes Alexander Shishkin
2010-09-16 22:30   ` john stultz
2010-09-16 22:58     ` Alexander Shishkin
2010-09-16 23:15       ` john stultz
2010-09-17  9:29   ` Thomas Gleixner
2010-10-01 13:23     ` Alexander Shishkin
2010-09-17 10:33   ` Alan Cox
2010-09-17 10:22     ` Kay Sievers
2010-09-17 11:08       ` Alexander Shishkin [this message]
2010-09-17 11:07     ` Thomas Gleixner
2010-09-16 22:10 ` [PATCH 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin
2010-09-16 22:10 ` [PATCH 3/7] wire up sys_time_change_notify() on x86 Alexander Shishkin
2010-09-16 22:10 ` [PATCH 4/7] wire up sys_time_change_notify() on powerpc Alexander Shishkin
2010-09-16 22:10 ` [PATCH 5/7] wire up sys_time_change_notify() on blackfin Alexander Shishkin
2010-09-22  7:45   ` Mike Frysinger
2010-09-16 22:10 ` [PATCH 6/7] wire up sys_time_change_notify() on ia64 Alexander Shishkin
2010-09-16 22:10 ` [PATCH 7/7] wire up sys_time_change_notify() on s390 Alexander Shishkin
2010-09-17 12:57 ` [PATCHv5 0/7] system time changes notification Thomas Gleixner
     [not found]   ` <AANLkTin2T3XX0b5ezzCvLvQiu0qg_KWfTSTaATHZmMk=@mail.gmail.com>
2010-09-17 13:52     ` Thomas Gleixner

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=20100917110803.GC10463@shisha.kicks-ass.net \
    --to=virtuoso@slind.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=avi@redhat.com \
    --cc=chris.friesen@genband.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=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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