On Fri, 2011-12-16 at 15:40 +0800, Zang Hongyong wrote:
于 2011/12/16,星期五 15:05, Sasha Levin 写道:
On Fri, 2011-12-16 at 13:32 +0800, zanghongy...@huawei.com wrote:
From: Hongyong Zangzanghongy...@huawei.com
Vhost-net uses its own vhost_memory, which results from user space (qemu)
info,
On Fri, 2011-12-16 at 09:59 +0200, Sasha Levin wrote:
There has been a great deal of effort to keep vhost and kvm untangled.
One example is the memory translation it has to do, another one is the
eventfd/irqfd thing it does just so it could signal an IRQ in the guest
instead of accessing the
于 2011/12/16,星期五 15:59, Sasha Levin 写道:
On Fri, 2011-12-16 at 15:40 +0800, Zang Hongyong wrote:
于 2011/12/16,星期五 15:05, Sasha Levin 写道:
On Fri, 2011-12-16 at 13:32 +0800, zanghongy...@huawei.com wrote:
From: Hongyong Zangzanghongy...@huawei.com
Vhost-net uses its own vhost_memory, which
From: Hongyong Zang zanghongy...@huawei.com
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
(2011/12/16 14:32), zanghongy...@huawei.com wrote:
From: Hongyong Zangzanghongy...@huawei.com
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
On Fri, 2011-12-16 at 13:32 +0800, zanghongy...@huawei.com wrote:
From: Hongyong Zang zanghongy...@huawei.com
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
于 2011/12/16,星期五 15:05, Sasha Levin 写道:
On Fri, 2011-12-16 at 13:32 +0800, zanghongy...@huawei.com wrote:
From: Hongyong Zangzanghongy...@huawei.com
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
