Revision 32ffa4f71e10009498ae6b54da65ab316db967bd authored by Axel Rasmussen on 19 May 2021, 20:03:33 UTC, committed by Paolo Bonzini on 27 May 2021, 11:45:55 UTC
This is a preparatory commit needed before we can use different kinds of
backing pages for guest memory.

Previously, we used perf_test_args.host_page_size, which is the host's
native page size (commonly 4K). For VM_MEM_SRC_ANONYMOUS this turns out
to be okay, but in a follow-up commit we want to allow using different
kinds of backing memory.

Take VM_MEM_SRC_ANONYMOUS_HUGETLB for example. Without this change, if
we used that backing page type, when we issued a UFFDIO_COPY ioctl we'd
only do so with 4K, rather than the full 2M of a backing hugepage. In
this case, UFFDIO_COPY returns -EINVAL (__mcopy_atomic_hugetlb checks
the size).

Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
Message-Id: <20210519200339.829146-5-axelrasmussen@google.com>
Reviewed-by: Ben Gardon <bgardon@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent 25408e5
History
File Mode Size
Kconfig -rw-r--r-- 1.1 KB
Makefile -rw-r--r-- 367 bytes
core.c -rw-r--r-- 12.9 KB
messaging.c -rw-r--r-- 9.1 KB
qcom-ctrl.c -rw-r--r-- 18.1 KB
qcom-ngd-ctrl.c -rw-r--r-- 41.2 KB
sched.c -rw-r--r-- 3.2 KB
slimbus.h -rw-r--r-- 16.3 KB
stream.c -rw-r--r-- 12.1 KB

back to top