On Mon, Apr 30, 2012 at 04:34:33PM +0300, Avi Kivity wrote: > Okay, sounds reasonable for the constraints you have. > > I guess you can still make the sizing automatic by deferring hash table > allocation until the first KVM_RUN (when you know the size of guest > memory) but that leads to awkward locking and doesn't mesh well with > memory hotplug. The trouble with waiting until the first KVM_RUN is that we have to tell the guest the size of the hash table via the device tree, which userspace has placed in guest memory. The kernel doesn't have any direct knowledge of the location or contents of the device tree. That's why I need an ioctl to enable the kernel and userspace to come to agreement about the size, so that userspace can then put the size in the device tree. Paul. -- 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
