Skip to content

RFC Introduce CLOCK_BOOTTIME

John Stultz lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2hrtimers: extend hrtimer base code to handle more then 2 clockidsinclude/linux/hrtimer.h kernel/hrtimer.c+33 -150 replies
1/2hrtimers: extend hrtimer base code to handle more then 2 clockidsinclude/linux/hrtimer.h kernel/hrtimer.c+33 -150 replies
2/2hrtimers: Add CLOCK_BOOTTIME clockid, hrtimerbase and posix interfaceinclude/linux/hrtimer.h include/linux/time.h kernel/hrtimer.c +2 more+113 -40 replies
2/2hrtimers: Add CLOCK_BOOTTIME clockid, hrtimerbase and posix interfaceinclude/linux/hrtimer.h include/linux/time.h kernel/hrtimer.c +2 more+113 -40 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] [RFC] Introduce CLOCK_BOOTTIME

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 <[email protected]>
CC Thomas Gleixner <[email protected]>
CC Alexander Shishkin <[email protected]>
CC Arve Hj�nnev�g <[email protected]>

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(-)
Signature · 1 line
1.7.3.2.146.gca209