Messages in this thread |  | | | From | John Stultz <> | | Subject | [PATCH 0/2] [RFC] Introduce CLOCK BOOTTIME | | Date | Wed, 15 Dec 2010 16:40:46 -0800 |
| |
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 |  |