On Fri, 2011-12-16 at 13:32 +0800, zanghongyong@xxxxxxxxxx wrote: > From: Hongyong Zang <zanghongyong@xxxxxxxxxx> > > Vhost-net uses its own vhost_memory, which results from user space (qemu) info, > to translate GPA to HVA. Since kernel's kvm structure already maintains the > address relationship in its member *kvm_memslots*, these patches use kernel's > kvm_memslots directly without the need of initialization and maintenance of > vhost_memory. Conceptually, vhost isn't aware of KVM - it's just a driver which moves data from vq to a tap device and back. You can't simply add KVM specific code into vhost. Whats the performance benefit? -- Sasha. -- 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
