From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xen.org>
Subject: Re: common time reference between domU and dom0
Date: Fri, 10 Dec 2010 10:00:38 +0000
Message-ID: <C927AAC6.C5A0%keir@xen.org>
References: <AEC6C66638C05B468B556EA548C1A77D01BB897F@trantor>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01BB897F@trantor>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: James Harper <james.harper@bendigoit.com.au>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 10/12/2010 08:23, "James Harper" <james.harper@bendigoit.com.au> 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