[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] common time reference between domU and dom0


  • To: "Keir Fraser" <keir@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.