From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: lkml@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
John Stultz <johnstul@us.ibm.com>,
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, linux-api@vger.kernel.org
Subject: Re: [PATCH] [RFC] notify userspace about time changes
Date: Thu, 5 Aug 2010 13:05:35 +0300 [thread overview]
Message-ID: <20100805100535.GA1754@shutemov.name> (raw)
In-Reply-To: <20100804154638.GB28519@shisha.kicks-ass.net>
On Wed, Aug 04, 2010 at 06:46:38PM +0300, Alexander Shishkin wrote:
> On Wed, Aug 04, 2010 at 06:32:21 +0300, Kirill A. Shutemov wrote:
> > On Wed, Aug 04, 2010 at 03:48:28PM +0300, Alexander Shishkin wrote:
> > > Certain userspace applications (like "clock" desktop applets or ntpd) 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.
> > >
> > > This patch implements a notification interface via eventfd mechanism. Proccess
> > > wishing to be notified about time changes should create an eventfd and echo
> > > its file descriptor to /sys/kernel/time_notify. After that, any calls to
> > > settimeofday()/stime()/adjtimex() made by other processes will be signalled
> > > to this eventfd. Credits for suggesting the eventfd mechanism for this
> > > purpose go te Kirill Shutemov.
> > >
> > > So far, this implementation can only filter out notifications caused by
> > > time change calls made by the process that wrote the eventfd descriptor to
> > > sysfs, but not its children which (might) have inherited the eventfd. It
> > > is so far not clear to me whether this is bad and more confusing than
> > > excluding such children as well.
> >
> > I think it's a bad idea to filter notifications. Let's leave it for
>
> Why?
Someone might want to recieve notifications about its own activity.
It's a policy. Kernel should provide mechanism, not policy.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2010-08-05 10:05 UTC|newest]
Thread overview: 29+ 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
[not found] ` <1280926108-24668-1-git-send-email-virtuoso-0lOfPCoBze7YtjvyW6yDsg@public.gmane.org>
2010-08-04 15:32 ` Kirill A. Shutemov
2010-08-04 15:32 ` Kirill A. Shutemov
2010-08-04 15:46 ` Alexander Shishkin
2010-08-05 10:05 ` Kirill A. Shutemov [this message]
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
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=20100805100535.GA1754@shutemov.name \
--to=kirill@shutemov.name \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=jkacur@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=jon-hunter@ti.com \
--cc=linux-api@vger.kernel.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.