On 05/23/2011 05:58 PM, Joerg Roedel wrote:
On Mon, May 23, 2011 at 05:34:20PM +0300, Avi Kivity wrote: > On 05/23/2011 05:28 PM, Joerg Roedel wrote: >> To user-space we can provide a VCPU_FREEZE/VCPU_UNFREEZE ioctl which >> does all the necessary things. > > Or we can automatically flush things on any exit to userspace. They > should be very rare in guest mode. This would make nesting mostly transparent to migration, so it sounds good in this regard. I do not completly agree that user-space exits in guest-mode are rare, this depends on the hypervisor in the L1. In Hyper-V for example the root-domain uses hardware virtualization too and has direct access to devices (at least to some degree). IOIO is not intercepted in the root-domain, for example. Not sure about the MMIO regions.
Good point. We were also talking about passing through virtio (or even host) devices to the guest.
So an ioctl to flush volatile state to memory would be a good idea. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
