summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorAckerley Tng <ackerleytng@google.com>2023-10-27 11:22:17 -0700
committerPaolo Bonzini <pbonzini@redhat.com>2023-11-14 08:01:09 -0500
commite3577788de64139202d89224fe31613c0f02b790 (patch)
treedb3fa59d7e8530d8be577bc1db5c1e5a90e0e786 /virt
parent8a89efd43423cb3005c5e641e846184e292c1465 (diff)
downloadlinux-e3577788de64139202d89224fe31613c0f02b790.tar.gz
linux-e3577788de64139202d89224fe31613c0f02b790.tar.bz2
linux-e3577788de64139202d89224fe31613c0f02b790.zip
KVM: selftests: Test KVM exit behavior for private memory/access
"Testing private access when memslot gets deleted" tests the behavior of KVM when a private memslot gets deleted while the VM is using the private memslot. When KVM looks up the deleted (slot = NULL) memslot, KVM should exit to userspace with KVM_EXIT_MEMORY_FAULT. In the second test, upon a private access to non-private memslot, KVM should also exit to userspace with KVM_EXIT_MEMORY_FAULT. Intentionally don't take a requirement on KVM_CAP_GUEST_MEMFD, KVM_CAP_MEMORY_FAULT_INFO, KVM_MEMORY_ATTRIBUTE_PRIVATE, etc., as it's a KVM bug to advertise KVM_X86_SW_PROTECTED_VM without its prerequisites. Signed-off-by: Ackerley Tng <ackerleytng@google.com> [sean: call out the similarities with set_memory_region_test] Signed-off-by: Sean Christopherson <seanjc@google.com> Message-Id: <20231027182217.3615211-36-seanjc@google.com> Reviewed-by: Fuad Tabba <tabba@google.com> Tested-by: Fuad Tabba <tabba@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions