From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Alexander Shishkin <virtuoso@slind.org>
Cc: 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: Wed, 4 Aug 2010 18:32:21 +0300 [thread overview]
Message-ID: <20100804153221.GA29109@shutemov.name> (raw)
In-Reply-To: <1280926108-24668-1-git-send-email-virtuoso@slind.org>
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
userspace. Userspace always can check eventfd counter and understand who
touch time based on its own activity.
> Similar mechanism can also be used for signalling other (all?) system calls
> made by certain (all?) processes without resorting to ptrace (which won't
> help if you don't know what processes you'd like to look after), given
> proper permission checks etc.
>
> Signed-off-by: Alexander Shishkin <virtuoso@slind.org>
> CC: Kirill A. Shutemov <kirill@shutemov.name>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: John Stultz <johnstul@us.ibm.com>
> CC: Martin Schwidefsky <schwidefsky@de.ibm.com>
> CC: Andrew Morton <akpm@linux-foundation.org>
> CC: Jon Hunter <jon-hunter@ti.com>
> CC: Ingo Molnar <mingo@elte.hu>
> CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> CC: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> CC: David Howells <dhowells@redhat.com>
> CC: Avi Kivity <avi@redhat.com>
> CC: "H. Peter Anvin" <hpa@zytor.com>
> CC: John Kacur <jkacur@redhat.com>
> CC: Alexander Shishkin <virtuoso@slind.org>
> CC: linux-kernel@vger.kernel.org
> ---
> include/linux/time.h | 7 ++
> init/Kconfig | 7 ++
> kernel/Makefile | 1 +
> kernel/time.c | 11 +++-
> kernel/time_notify.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 182 insertions(+), 2 deletions(-)
> create mode 100644 kernel/time_notify.c
>
> diff --git a/include/linux/time.h b/include/linux/time.h
> index ea3559f..9fca62b 100644
> --- a/include/linux/time.h
> +++ b/include/linux/time.h
> @@ -237,6 +237,13 @@ static __always_inline void timespec_add_ns(struct timespec *a, u64 ns)
> a->tv_sec += __iter_div_u64_rem(a->tv_nsec + ns, NSEC_PER_SEC, &ns);
> a->tv_nsec = ns;
> }
> +
> +#ifdef CONFIG_TIME_NOTIFY
> +void time_notify_all(void);
> +#else
> +#define time_notify_all() do {} while (0)
> +#endif
> +
> #endif /* __KERNEL__ */
>
> #define NFDBITS __NFDBITS
> diff --git a/init/Kconfig b/init/Kconfig
> index 5cff9a9..f7271f8 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -976,6 +976,13 @@ config PERF_USE_VMALLOC
> help
> See tools/perf/design.txt for details
>
> +config TIME_NOTIFY
> + bool
> + depends on EVENTFD
> + help
> + Enable time change notification events to userspace via
> + eventfd.
> +
Do we really need config option? I think better just use
CONFIG_EVENTFD.
linux-api@vger.kernel.org added to CC list.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2010-08-04 15:32 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 [this message]
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
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=20100804153221.GA29109@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 \
--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