From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Galibert Subject: Re: Attempted summary of suspend-blockers LKML thread Date: Wed, 4 Aug 2010 06:58:13 +0200 Message-ID: <20100804045813.GA33951@dspnet.fr> References: <20100804001015.GJ2407@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Arve =?iso-8859-1?B?SGr4bm5lduVn?= Cc: david@lang.hm, Ted Ts'o , peterz@infradead.org, swetland@google.com, linux-kernel , florian@mickler.org, linux-pm@lists.linux-foundation.org, "Paul E. McKenney" , tglx@linutronix.de, alan@lxorguk.ukuu.org.uk, Arjan van de Ven List-Id: linux-pm@vger.kernel.org On Tue, Aug 03, 2010 at 08:39:22PM -0700, Arve Hj=F8nnev=E5g 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. OG.