WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] System time monotonicity

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] System time monotonicity
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Mon, 26 Mar 2007 21:04:47 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 26 Mar 2007 13:00:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C22DD3E5.4D2F%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070326182323.GA30728@xxxxxxxxxxxxxxxxxxxxxxx> <C22DD3E5.4D2F%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Mar 26, 2007 at 07:47:49PM +0100, Keir Fraser wrote:

> >> From what I can work out, time is supposed to be monotonic but I admit I
> > can't really understand the time code yet at least. I couldn't find any
> > documentation on what to expect from system time. Any suggestions?
> > 
> > This seems to happen across all the hardware we've tried but this
> > particular case is a Sun V20Z with two CPUs:
> > 
> >   x86 (AuthenticAMD family 15 model 5 step 10 clock 2392 MHz)
> >         AMD Opteron(tm) Processor 250
> 
> Small backwards time deltas are possible from the current time code. You'll
> have to filter them out yourself if you can't deal with them. We could add
> extra code in Xen to stop this happening for any individual VCPU

Some instrumentation indicated that we had cross-VCPU jitter of
significant deltas, ~18us at worst. Though the instrumentation wasn't
completely reliable so that might not be accurate.

On real hardware we deal with any jitter via comparing against a regular
clock on CPU0. This obviously won't work for Xen since we have no
control over where VCPU0 actually lives. Presumably the Linux code
(monotonic_clock() especially) must have something to handle it, but I
can't see where...

regards
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel