From: John Stultz <john.stultz@linaro.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "John Stultz" <john.stultz@linaro.org>,
"Jamie Lokier" <jamie@shareable.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Alexander Shishkin" <virtuoso@slind.org>,
"Arve Hj�nnev�g" <arve@android.com>
Subject: [PATCH 0/2] [RFC] Introduce CLOCK_BOOTTIME
Date: Wed, 15 Dec 2010 16:40:46 -0800 [thread overview]
Message-ID: <1292460048-28035-1-git-send-email-john.stultz@linaro.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1874 bytes --]
After some discussions with Jamie Lokier about some of the
drawbacks of CLOCK_MONOTONIC not incrementing during suspend
(see http://www.spinics.net/lists/linux-fsdevel/msg40272.html),
I wanted to see if we couldn't provide a new clockid that would
allow applications that wanted to be aware of time passing during
suspend without having to deal with the inconsistencies of
CLOCK_REALTIME caused by calls to settimeofday.
So this patchset introduces CLOCK_BOOTTIME, which is identical
to CLOCK_MONOTONIC, but includes any time spent in suspend.
This is just my initial stab at this, so I'd appreciate any comments
or thougths on these patches.
Jamie: On platforms that don't implement read_persistent_clock,
your issue would still be present, but fixing that is on my list.
Other then that issue, does this seem to address your concern?
Thomas: Let me know if the hrtimer_base indirection is too
gross. It just seemed silly to create 5 empty bases so we could
have an exact match between the clockids and the bases.
Arve: I believe CLOCK_BOOTTIME would be sufficient for what
Android is using as elapsedRealtime() or
ANDROID_ALARM_ELAPSED_REALTIME. If not please let me know why.
thanks
-john
CC: Jamie Lokier <jamie@shareable.org>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Alexander Shishkin <virtuoso@slind.org>
CC: Arve Hjønnevåg <arve@android.com>
John Stultz (2):
hrtimers: extend hrtimer base code to handle more then 2 clockids
hrtimers: Add CLOCK_BOOTTIME clockid, hrtimerbase and posix interface
include/linux/hrtimer.h | 22 ++++++++++++-
include/linux/time.h | 4 ++
kernel/hrtimer.c | 44 ++++++++++++++++---------
kernel/posix-timers.c | 16 ++++++++-
kernel/time/timekeeping.c | 79 ++++++++++++++++++++++++++++++++++++++++++++-
5 files changed, 146 insertions(+), 19 deletions(-)
--
1.7.3.2.146.gca209
next reply other threads:[~2010-12-16 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 0:40 John Stultz [this message]
2010-12-16 0:40 ` [PATCH 1/2] hrtimers: extend hrtimer base code to handle more then 2 clockids John Stultz
2010-12-16 0:40 ` [PATCH 2/2][RFC] hrtimers: Add CLOCK_BOOTTIME clockid, hrtimerbase and posix interface John Stultz
2010-12-16 0:47 ` John Stultz
2010-12-16 0:43 ` [PATCH 1/2][RFC] hrtimers: extend hrtimer base code to handle more then 2 clockids 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=1292460048-28035-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=arve@android.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome