From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Re: common time reference between domU and dom0 Date: Fri, 10 Dec 2010 22:41:44 +0100 Message-ID: <4D029E98.2030702@redhat.com> References: <4D01FF82.5000106@redhat.com C927B553.C5BB%keir@xen.org> <94800155-be30-4597-9514-95221e4979c1@default> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <94800155-be30-4597-9514-95221e4979c1@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: James Harper , Keir Fraser , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 12/10/2010 09:27 PM, Dan Magenheimer wrote: > Urk. Paolo, I hope Redhat isn't using HVMOP_get_time now as a basis > for pvops time? No. I only plan to use it in Windows guests. That said... > That was one of the purposes of all the tsc work > in 4.0 so selecting TSC as the clocksource should have the same > result (and IIRC the trap is faster than the hypercall). ... this has not been backported to RHEL5 though. Paolo