On Tue, Feb 09, 2021 at 02:49:39PM +0100, David Hildenbrand wrote: > Let's provide a way to control the use of RAM_NORESERVE via memory > backends using the "reserve" property which defaults to true (old > behavior). > > Only POSIX supports setting the flag (and Linux support is checked at > runtime, depending on the setting of "/proc/sys/vm/overcommit_memory"). > Windows will bail out. > > The target use case is virtio-mem, which dynamically exposes memory > inside a large, sparse memory area to the VM. This essentially allows > avoiding to set "/proc/sys/vm/overcommit_memory == 0") when using > virtio-mem and also supporting hugetlbfs in the future. > > Signed-off-by: David Hildenbrand <da...@redhat.com>
Reviewed-by: Peter Xu <pet...@redhat.com> -- Peter Xu