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: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] common time reference between domU and dom0
From: Keir Fraser <keir@xxxxxxx>
Date: Fri, 10 Dec 2010 10:45:08 +0000
Cc:
Delivery-date: Fri, 10 Dec 2010 02:46:02 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=dImAJV1W0j/FQUVJktWgVQmXN4c6e9juyfslvYi53z8=; b=Sz1FIdV6ARKg0T2xTlvSo3PH6tYzSCGsIpe6TLho7w5Di5jBll1qzs6CSBn3uJTJHt mR+xzJzsDjCFRuxUqIP23cx7vTAQMOyPbQNps59oOdaqyYTnY4JaBavhpiG8FAmjVvQn ReqNgJn8wxxFHA8BOwoMGdK4vuB6iipo94dBs=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01BB8980@trantor>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuYKlmfwlYiX5ejQNegrVc1bZJ6nwAEEnxiAAI5plAAA2OS5gAAoqAAAADrPI8=
Thread-topic: [Xen-devel] common time reference between domU and dom0
User-agent: Microsoft-Entourage/12.27.0.100910
On 10/12/2010 10:20, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

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

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.

 -- Keir

> James
> 



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