[Xen-devel] Re: rdtsc hypercall, from userland?!? (was: rdtsc: correctness vs performance on Xen)

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

On 09/09/09 11:05, Dan Magenheimer wrote:
>  BUT
> (IMPORTANT NEW POINT!!!) the pvclock algorithm requires
> an rdtsc instruction, and there is no way to
> emulate some guest rdtsc instructions (e.g. only
> those in apps) and not others (e.g. only those in
> the kernel).  Thus, for guests that have rdtsc emulation
> enabled, vsyscall+pvclock will be SLOWER than emulation,
> thus meaning it is still not a palatable alternative.
>   

You could enable/disable emulation rdtsc each context switch according
to the app's desires/requrements.  It would require an extra hypercall
per context switch, but it could be batched with the others, resulting
in little marginal cost.  It would, however, leave the kernel's use of
rdtsc in a confused state.

    J


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