summaryrefslogtreecommitdiffstats
path: root/Documentation/RCU/torture.rst
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-03-09 11:20:44 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2024-03-09 11:42:17 -0500
commit39fee313fdd489480eb2c453535ab73672c39a27 (patch)
treead213f2466882fe81e760eba3092c1e112e6ea19 /Documentation/RCU/torture.rst
parent1b6c146df555bcfb9ad55dbb745ee364a9a0159f (diff)
parent2dfd2383034421101300a3b7325cf339a182d218 (diff)
downloadlinux-stable-39fee313fdd489480eb2c453535ab73672c39a27.tar.gz
linux-stable-39fee313fdd489480eb2c453535ab73672c39a27.tar.bz2
linux-stable-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 'Documentation/RCU/torture.rst')
0 files changed, 0 insertions, 0 deletions