On 19.09.23 10:20, David Hildenbrand wrote:
On 11.09.23 09:45, David Hildenbrand wrote:
@MST, any comment on the vhost bits (mostly uncontroversial and only in
the memslot domain)?
I'm planning on queuing this myself (but will wait a bit more), unless
you want to take it.
I'm queuing this to
On 11.09.23 09:45, David Hildenbrand wrote:
@MST, any comment on the vhost bits (mostly uncontroversial and only in
the memslot domain)?
I'm planning on queuing this myself (but will wait a bit more), unless
you want to take it.
I'm queuing this to
@MST, any comment on the vhost bits (mostly uncontroversial and only in
the memslot domain)?
I'm planning on queuing this myself (but will wait a bit more), unless
you want to take it.
On 08.09.23 16:21, David Hildenbrand wrote:
Quoting from patch #14:
Having large virtio-mem devices
Quoting from patch #14:
Having large virtio-mem devices that only expose little memory to a VM
is currently a problem: we map the whole sparse memory region into the
guest using a single memslot, resulting in one gigantic memslot in KVM.
KVM allocates metadata for the whole
