summaryrefslogtreecommitdiff
path: root/virt/kvm/Kconfig
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-01-06 02:24:00 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2024-01-08 08:09:38 -0500
commit3a373e027d8b0ed14963cc84b48a11e69e4506b6 (patch)
treeb706ff192245bf2543f9637daa59c9527a7c4c0c /virt/kvm/Kconfig
parentcaadf876bb7449bf25ef817afe7fb881df8198a2 (diff)
KVM: fix direction of dependency on MMU notifiers
KVM_GENERIC_MEMORY_ATTRIBUTES requires the generic MMU notifier code, because it uses kvm_mmu_invalidate_begin/end. However, it would not work with a bespoke implementation of MMU notifiers that does not use KVM_GENERIC_MMU_NOTIFIER, because most likely it would not synchronize correctly on invalidation. So the right thing to do is to note the problematic configuration if the architecture does not select itself KVM_GENERIC_MMU_NOTIFIER; not to enable it blindly. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt/kvm/Kconfig')
-rw-r--r--virt/kvm/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/virt/kvm/Kconfig b/virt/kvm/Kconfig
index ace72be98fb2..184dab4ee871 100644
--- a/virt/kvm/Kconfig
+++ b/virt/kvm/Kconfig
@@ -97,7 +97,7 @@ config KVM_GENERIC_MMU_NOTIFIER
bool
config KVM_GENERIC_MEMORY_ATTRIBUTES
- select KVM_GENERIC_MMU_NOTIFIER
+ depends on KVM_GENERIC_MMU_NOTIFIER
bool
config KVM_PRIVATE_MEM