From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 2/3] xen: add correct 500 ms offset when setting Xen wallclock Date: Mon, 15 Oct 2012 13:21:36 +0100 Message-ID: <507BFFD0.2010707@citrix.com> References: <1350046634-2462-1-git-send-email-david.vrabel@citrix.com> <1350046634-2462-3-git-send-email-david.vrabel@citrix.com> <1350293121.18058.10.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1350293121.18058.10.camel@zakaz.uk.xensource.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: Ian Campbell Cc: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 15/10/12 10:25, Ian Campbell wrote: > On Fri, 2012-10-12 at 13:57 +0100, David Vrabel wrote: >> From: David Vrabel >> >> update_persistent_wallclock() (and hence xet_set_wallclock()) is >> called 500 ms after the second. > > The comment in sync_cmos_clock says it is called 500ms before the next > second. This is the same thing, right? > I only mention it to double check that the right semantics for > set_wallclock are being implemented, i.e. that we are compensating in > the right direction. I'll add some debug code to make sure. David