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

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


  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
  • Date: Fri, 10 Dec 2010 11:22:58 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 10 Dec 2010 02:23:34 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jVRitlIp7BWijKV68d0qoneOdiRML0YaB0KNBy+LegAgWk8WeCJGBkfnDgi/+wMVo5 oqe4ILfzT7lbiA0gaiqlVaSVR3HmW/raCDCuslsG2tSqB8a3azv/IAzDyTeGgwiDR26l i/3u80a3w9TNCY4Y2S5Yn8eZaSxkrennAteUo=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 12/10/2010 11:20 AM, James Harper wrote:
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?

Not really, but it is really an easy backport to your hypervisor. It will even be in RHEL5.6/CentOS 5.6.

Paolo

_______________________________________________
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®.