diff options
| author |   Paolo Bonzini <pbonzini@redhat.com> | 2024-03-09 11:20:44 -0500 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-03-09 11:42:17 -0500 |
| commit | 39fee313fdd489480eb2c453535ab73672c39a27 (patch) | |
| tree | ad213f2466882fe81e760eba3092c1e112e6ea19 /net/unix/af_unix.c | |
| parent | Merge tag 'kvm-x86-fixes-6.8-2' of https://github.com/kvm-x86/linux into HEAD (diff) | |
| parent | KVM: selftests: Add a testcase to verify GUEST_MEMFD and READONLY are exclusive (diff) | |
| download | wireguard-linux-39fee313fdd489480eb2c453535ab73672c39a27.tar.xz wireguard-linux-39fee313fdd489480eb2c453535ab73672c39a27.zip | |
Merge tag 'kvm-x86-guest_memfd_fixes-6.8' of https://github.com/kvm-x86/linux into HEAD
KVM GUEST_MEMFD fixes for 6.8:
- Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY to
avoid creating ABI that KVM can't sanely support.
- Update documentation for KVM_SW_PROTECTED_VM to make it abundantly
clear that such VMs are purely a development and testing vehicle, and
come with zero guarantees.
- Limit KVM_SW_PROTECTED_VM guests to the TDP MMU, as the long term plan
is to support confidential VMs with deterministic private memory (SNP
and TDX) only in the TDP MMU.
- Fix a bug in a GUEST_MEMFD negative test that resulted in false passes
when verifying that KVM_MEM_GUEST_MEMFD memslots can't be dirty logged.
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions