On Fri, Mar 05, 2021 at 11:16:34AM +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. > > Reviewed-by: Peter Xu <pet...@redhat.com> > Signed-off-by: David Hildenbrand <da...@redhat.com>
Reviewed-by: Eduardo Habkost <ehabk...@redhat.com> Paolo, will the whole series get through your memory API queue? Also, do you think we should move backends/hostmem* under the "memory API" section in MAINTAINERS? Most memory backend changes also involve changes in the memory API. -- Eduardo
