From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Magenheimer" Subject: RE: RE: [PATCH] record max stime skew (was RE: [PATCH] strictly increasing hvm guest time) Date: Thu, 3 Jul 2008 10:35:48 -0600 Message-ID: <20080703103548140.00000003744@djm-pc> References: <20080703102413734.00000003744@djm-pc> Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080703102413734.00000003744@djm-pc> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "dan.magenheimer@oracle.com" , Keir Fraser , "Xen-Devel (E-mail)" Cc: Dave Winchell List-Id: xen-devel@lists.xenproject.org > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com]On Behalf Of Dan > Magenheimer > Subject: [Xen-devel] RE: [PATCH] record max stime skew (was = > = > > Perhaps this relatively large skew happens at start of day, = > before the > > periodic calibration has 'locked on'? > = > Indeed you are correct. This updated patch now reports zero skew > as expected. > = > IMHO, it would be nice to put this patch into the tree as it > will be good for helping to diagnose time skew problems > such as the one just reported on the list. Oops! Just after I sent the above email, I checked again and the same machine (no reboots, no guests ever launched) now reports a max stime skew of 4333ns!! Methinks there might be some periodic glitch in the calibration code? Dan