From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Wroblewski Subject: Re: TSC trouble in hvm linux, after host S3 Date: Wed, 20 Nov 2013 13:07:15 +0100 Message-ID: <528CA5F3.5000307@citrix.com> References: <528C95AE.6040308@citrix.com> <528C9FF0.2050706@citrix.com> <528CB0510200007800104FC0@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vj6ZB-0001js-IS for xen-devel@lists.xenproject.org; Wed, 20 Nov 2013 12:07:33 +0000 In-Reply-To: <528CB0510200007800104FC0@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel List-Id: xen-devel@lists.xenproject.org > This sounds plausible, but I'd prefer it to be done alongside the other > state resetting done for S3 (which all happen in hvm_s3_suspend()). > Unless that doesn't work, of course. > looks like it has to be done after resume since set_guest_tsc reads current timestamp to determine the offset necessary, and for the logic to be correct it needs to do it after it's already been reset to 0 on the host. > Jan >