From: john stultz <johnstul@us.ibm.com>
To: Alexander Shishkin <virtuoso@slind.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@suse.de>,
Feng Tang <feng.tang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Tokarev <mjt@tls.msk.ru>,
Marcelo Tosatti <mtosatti@redhat.com>,
Chris Friesen <chris.friesen@genband.com>,
Kay Sievers <kay.sievers@vrfy.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Artem Bityutskiy <dedekind1@gmail.com>,
Davide Libenzi <davidel@xmailserver.org>,
Lennart Poettering <mzxreary@0pointer.de>,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] timerfd: add TFD_NOTIFY_CLOCK_SET to watch for clock changes
Date: Wed, 01 Dec 2010 16:14:27 -0800 [thread overview]
Message-ID: <1291248867.2846.37.camel@work-vm> (raw)
In-Reply-To: <1291167587-16695-1-git-send-email-virtuoso@slind.org>
On Wed, 2010-12-01 at 03:39 +0200, Alexander Shishkin wrote:
> To use this notification functionality, user has to call timerfd_settime()
> with TFD_NOTIFY_CLOCK_SET flag. After this CLOCK_REALTIME timers will
> read as the number of times the wall clock has been set since last read
> and poll every time the wall clock is set; CLOCK_MONOTONIC timers will
> behave likewise, but in the event of the clock being updated upon resuming
> from suspend. For both CLOCK_REALTIME and CLOCK_MONOTONIC timers with
> TFD_NOTIFY_CLOCK_SET flag set, a call to timerfd_gettime() will return
> current wall clock in it_value.
The CLOCK_MONOTONIC flag on resume worries me a bit (since
CLOCK_MONOTONIC isn't adjusted on resume).
What is the use case there?
thanks
-john
next prev parent reply other threads:[~2010-12-02 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 1:39 [PATCH] timerfd: add TFD_NOTIFY_CLOCK_SET to watch for clock changes Alexander Shishkin
2010-12-02 0:14 ` john stultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-09 14:30 Alexander Shishkin
2011-03-09 14:31 ` Alexander Shishkin
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=1291248867.2846.37.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@genband.com \
--cc=davidel@xmailserver.org \
--cc=dedekind1@gmail.com \
--cc=feng.tang@intel.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mtosatti@redhat.com \
--cc=mzxreary@0pointer.de \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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