[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=pwyidtK7aebRwZ+SsJCSS-6t=6cFffdvcKKnx@mail.gmail.com>
Date: Tue, 3 Aug 2010 23:03:15 -0700
From: Arve Hjønnevåg <arve@...roid.com>
To: Olivier Galibert <galibert@...ox.com>
Cc: david@...g.hm, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Arjan van de Ven <arjan@...radead.org>,
"Ted Ts'o" <tytso@....edu>, linux-pm@...ts.linux-foundation.org,
linux-kernel <linux-kernel@...r.kernel.org>, mjg59@...f.ucam.org,
pavel@....cz, florian@...kler.org, rjw@...k.pl,
stern@...land.harvard.edu, swetland@...gle.com,
peterz@...radead.org, tglx@...utronix.de, alan@...rguk.ukuu.org.uk
Subject: Re: Attempted summary of suspend-blockers LKML thread
2010/8/3 Olivier Galibert <galibert@...ox.com>:
> On Tue, Aug 03, 2010 at 08:39:22PM -0700, Arve Hjønnevåg wrote:
>> If you just program the alarm you will wake up see that the monotonic
>> clock has not advanced and set the alarm another n seconds into the
>> future. Or are proposing that suspend should be changed to keep the
>> monotonic clock running?
>
> You're supposed to fix the clock after you wake up. That's part of
> the cost of going suspend.
I'm not sure what you are referring to. The generic Linux timekeeping
code makes sure the monotonic clock stops while the system is
suspended regardless of what values the (hardware specific)
clocksource returns.
--
Arve Hjønnevåg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists