diff options
| author |  Sean Christopherson <seanjc@google.com>
| 2024-02-22 11:06:12 -0800 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com>
| 2024-02-22 17:07:06 -0800 |
| commit | 2dfd2383034421101300a3b7325cf339a182d218 (patch) | |
| tree | b8de7f5f2948fd44ed7b5388969fc98de6c8e591 /arch/x86/kvm/x86.c | |
| parent | KVM: selftests: Create GUEST_MEMFD for relevant invalid flags testcases (diff) | |
| download | linux-2dfd2383034421101300a3b7325cf339a182d218.tar.gz linux-2dfd2383034421101300a3b7325cf339a182d218.tar.bz2 linux-2dfd2383034421101300a3b7325cf339a182d218.zip | |
KVM: selftests: Add a testcase to verify GUEST_MEMFD and READONLY are exclusive
Extend set_memory_region_test's invalid flags subtest to verify that
GUEST_MEMFD is incompatible with READONLY. GUEST_MEMFD doesn't currently
support writes from userspace and KVM doesn't support emulated MMIO on
private accesses, and so KVM is supposed to reject the GUEST_MEMFD+READONLY
in order to avoid configuration that KVM can't support.
Link: https://lore.kernel.org/r/20240222190612.2942589-6-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'arch/x86/kvm/x86.c')
0 files changed, 0 insertions, 0 deletions