cloud-hypervisor/vmm
Sebastien Boeuf 3edc2bd6ab vmm: Prevent memory overcommitment through virtio-fs shared regions
When a virtio-fs device is created with a dedicated shared region, by
default the region should be mapped as PROT_NONE so that no pages can be
faulted in.

It's only when the guest performs the mount of the virtiofs filesystem
that we can expect the VMM, on behalf of the backend, to perform some
new mappings in the reserved shared window, using PROT_READ and/or
PROT_WRITE.

Fixes #763

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-02-17 15:03:47 +01:00
..
src vmm: Prevent memory overcommitment through virtio-fs shared regions 2020-02-17 15:03:47 +01:00
Cargo.toml vmm: Add support for spawning vhost-user-net backend 2020-02-14 17:32:49 +00:00