Messages in this thread | | | Date | Wed, 2 Jun 2010 09:21:52 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) |
| |
On Wed, 2 Jun 2010, Arve Hjønnevåg wrote: > 2010/6/2 Thomas Gleixner <tglx@linutronix.de>: > > On Tue, 1 Jun 2010, Arve Hjønnevåg wrote: > >> Deferring the the timers forever without stopping the clock can cause > >> problems. Our user space code has a lot of timeouts that will trigger > >> an error if an app does not respond in time. Freezing everything and > >> stopping the clock while suspended is a lot simpler than trying to > >> stop individual timers and processes from running. > > > > And resume updates timekeeping to account for the slept time. So the > > No, for the monotonic clock it does the opposite. The hardware clock > is read on resume and the offset is set so the monotonic clock gets > the same value as it had when suspend was called.
Grr, yes. Misread the code. -ENOTENOUGHCOFFEE
Thanks,
tglx | |