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] common time reference between domU and dom0

To: "Keir Fraser" <keir@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] common time reference between domU and dom0
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 10 Dec 2010 21:20:49 +1100
Cc:
Delivery-date: Fri, 10 Dec 2010 02:21:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C927AAC6.C5A0%keir@xxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01BB897F@trantor> <C927AAC6.C5A0%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuYKlmfwlYiX5ejQNegrVc1bZJ6nwAEEnxiAAI5plAAA2OS5gAAoqAA
Thread-topic: [Xen-devel] common time reference between domU and dom0
> On 10/12/2010 08:23, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> >>
> >> System time, as exposed to guests by Xen, should be good enough.
> >>
> >
> > How is this exposed for HVM systems?
> 
> Given all HVM guest time sources are trapped to the hypervisor,
including
> TSC, you may as well just use the HVMOP_get_time hypercall.
> 

Is that a new call? I don't see it mentioned in 4.0-testing anywhere.

Is there a fallback if HVMOP_get_time doesn't exist?

James


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