[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] common time reference between domU and dom0
- To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <keir@xxxxxxx>
- Date: Fri, 10 Dec 2010 10:45:08 +0000
- Delivery-date: Fri, 10 Dec 2010 02:46:02 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=qEEnKxwFv0Wba0yq367Wf0QbePqvGF9/0JXAz049mKktzt7uI27r0W5oN80EMfAYOK BHJdi45P8QaORtHlxoIgXqYPuQ3INbToKPYTlz0igkGdDDe/T5J4FPXHaSWQRimOeFyR JHgidQRJ9K2Nif6waIaxzmD3Tnx5MklE+YZUc=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcuYKlmfwlYiX5ejQNegrVc1bZJ6nwAEEnxiAAI5plAAA2OS5gAAoqAAAADrPI8=
- Thread-topic: [Xen-devel] common time reference between domU and dom0
On 10/12/2010 10:20, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:
>> On 10/12/2010 08:23, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
>>>> 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,
>> 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.
Yeah I think it's in 4.1 only.
> Is there a fallback if HVMOP_get_time doesn't exist?
Switch on vtsc (might be default) and just use RDTSC? Might be good enough.
I'm not sure that computing system time yourself from fields in shared info
works well for HVM guests. HVMOP_get_time I think had been in XenServer
patch queue a while and has just been pulled across to upstream.
Xen-devel mailing list