RE: [Xen-devel] Re: common time reference between domU and dom0

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

Urk.  Paolo, I hope Redhat isn't using HVMOP_get_time now as a basis
for pvops time?  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).

> -----Original Message-----
> From: Keir Fraser [mailto:keir@xxxxxxx]
> Sent: Friday, December 10, 2010 3:46 AM
> To: Paolo Bonzini; James Harper
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Re: common time reference between domU and
> dom0
> 
> On 10/12/2010 10:22, "Paolo Bonzini" <pbonzini@xxxxxxxxxx> wrote:
> 
> > On 12/10/2010 11:20 AM, James Harper wrote:
> >> Is that a new call? I don't see it mentioned in 4.0-testing
> anywhere.
> >>
> >> Is there a fallback if HVMOP_get_time doesn't exist?
> >
> > Not really, but it is really an easy backport to your hypervisor.  It
> > will even be in RHEL5.6/CentOS 5.6.
> 
> It's probably worth backporting for 4.0.2 too.
> 
>  -- Keir
> 
> > Paolo
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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