[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:00:38 +0000
- Cc:
- Delivery-date: Fri, 10 Dec 2010 02:02:20 -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=FWGd6GjS7FlPlMpMgT2dAqncrdn33tPGJZrIc+az6Kh5MxYs4Z2flogKKYLmLwhPEX I/XuZjcbaeQYM4v2WSl4KAf5RZRZNxc+d+a0xdo5zg7vBB5yLDM/WObrZ8gVcUNyRXcp mDzkkujMBQYkzr/KxnGAsUOwS7Kq+qxSidrtE=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcuYKlmfwlYiX5ejQNegrVc1bZJ6nwAEEnxiAAI5plAAA2OS5g==
- 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.
-- Keir
> James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
