[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] replace rdtsc emulation-vs-native xen boot option with per-domain (hypervisor part)


  • To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 06 Oct 2009 14:59:21 +0100
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 06 Oct 2009 07:01:55 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpGi/kqOznuvMbQTkSWF/OtyVZnkwAATrSw
  • Thread-topic: [Xen-devel] [PATCH] replace rdtsc emulation-vs-native xen boot option with per-domain (hypervisor part)

On 06/10/2009 14:49, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> This was intended to record the offset across migration.
> But a per-domain stime offset must already be recorded
> somewhere else, or hvm fully-emulated platform timers
> would be broken across migration.
> 
> Do pv guests need something similar or is it magically
> handled someplace that I couldn't quickly find?

PV guests understand that there will be a system-time discontinuity across
save/restore. All I did was remove an unused field. You can reintro it when
you use it.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.