diff options
| author | Sean Christopherson <seanjc@google.com> | 2023-10-27 11:21:48 -0700 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2023-11-13 05:29:09 -0500 |
| commit | 4a2e993faad3880962540ab8e3b68f22e48b18e8 (patch) | |
| tree | 33bae983cad6eb6a83b71cc959afb1591fed5410 /virt | |
| parent | 1853d7502a19b34b2cfe4ea0698bee73323fec3a (diff) | |
| download | linux-stable-4a2e993faad3880962540ab8e3b68f22e48b18e8.tar.gz linux-stable-4a2e993faad3880962540ab8e3b68f22e48b18e8.tar.bz2 linux-stable-4a2e993faad3880962540ab8e3b68f22e48b18e8.zip | |
KVM: PPC: Return '1' unconditionally for KVM_CAP_SYNC_MMU
Advertise that KVM's MMU is synchronized with the primary MMU for all
flavors of PPC KVM support, i.e. advertise that the MMU is synchronized
when CONFIG_KVM_BOOK3S_HV_POSSIBLE=y but the VM is not using hypervisor
mode (a.k.a. PR VMs). PR VMs, via kvm_unmap_gfn_range_pr(), do the right
thing for mmu_notifier invalidation events, and more tellingly, KVM
returns '1' for KVM_CAP_SYNC_MMU when CONFIG_KVM_BOOK3S_HV_POSSIBLE=n
and CONFIG_KVM_BOOK3S_PR_POSSIBLE=y, i.e. KVM already advertises a
synchronized MMU for PR VMs, just not when CONFIG_KVM_BOOK3S_HV_POSSIBLE=y.
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20231027182217.3615211-7-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions