From: Ingo Molnar Subject: Re: [PATCH] x86/pvclock-xen: zero last_value on resume Date: Fri, 26 Nov 2010 11:40:47 +0100 Message-ID: <20101126104047.GA9798@elte.hu> References: <4CC708DE.1070000@goop.org> <4CEACFAB.90503@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Xen-devel@lists.xensource.com" , kvm-devel , Glauber Costa , the arch/x86 maintainers , Linux Kernel Mailing List , Linux Virtualization , Olivier Hanesse , Avi Kivity , "H. Peter Anvin" , Thomas Gleixner , Eelco Dolstra To: Jeremy Fitzhardinge Return-path: Content-Disposition: inline In-Reply-To: <4CEACFAB.90503@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com List-Id: kvm.vger.kernel.org * Jeremy Fitzhardinge wrote: > On 10/26/2010 09:59 AM, Jeremy Fitzhardinge wrote: > > > > If the guest domain has been suspend/resumed or migrated, then the > > system clock backing the pvclock clocksource may revert to a smaller > > value (ie, can be non-monotonic across the migration/save-restore). > > Make sure we zero last_value in that case so that the domain > > continues to see clock updates. > > Ping? Looks like this fell through the gaps. Does not apply cleanly here - mind resending the latest version? Thanks, Ingo