Sebastien Boeuf 9c3166237d 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>
(cherry picked from commit 3edc2bd6ab)

2020-02-20 15:41:00 +00:00

..

src

vmm: Prevent memory overcommitment through virtio-fs shared regions

2020-02-20 15:41:00 +00:00

Cargo.toml

build(deps): bump kvm-ioctls from 0.4.0 to 0.5.0

2020-01-29 10:22:51 +00:00