On 05/23/2011 05:28 PM, Joerg Roedel wrote:
On Mon, May 23, 2011 at 04:52:47PM +0300, Avi Kivity wrote: > On 05/23/2011 04:40 PM, Joerg Roedel wrote: >> The next benefit is that it works seemlessly even if the state that >> needs to be transfered is extended (e.g. by emulating a new >> virtualization hardware feature). This support can be implemented in the >> kernel module and no changes to qemu are required. > > I agree it's a benefit. But I don't like making the fake vmexit part of > live migration, if it turns out the wrong choice it's hard to undo it. Well, saving the state to the host-save-area and doing a fake-vmexit is logically the same, only the memory where the information is stored differs.
Right. I guess the main difference is "info registers" after a stop.
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.
-- 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
