On 15/05/12 14:24, Avi Kivity wrote: >> Newer systems allow to write-protect the guest backing memory >> and let the fault be delivered to the host, thus allowing COW. >> >> Use a capability bit to tell qemu if that is possible. >> > > Asking out of ignorance: who is doing the write protection here? The > guest? If so, why is qemu involved? It is about the host doing write protection of guest/user memory (e.g. for dirty pages tracking or KSM) > btw, we usually use 'userspace' in kernel patches instead of qemu to > create the illusion that it's not the only consumer of kvm interfaces. In fact there are other consumers. -- 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
