diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2024-01-06 02:24:00 -0500 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-01-08 08:09:38 -0500 |
commit | 3a373e027d8b0ed14963cc84b48a11e69e4506b6 (patch) | |
tree | b706ff192245bf2543f9637daa59c9527a7c4c0c /scripts/coccinelle/misc/orplus.cocci | |
parent | caadf876bb7449bf25ef817afe7fb881df8198a2 (diff) | |
download | linux-stable-3a373e027d8b0ed14963cc84b48a11e69e4506b6.tar.gz linux-stable-3a373e027d8b0ed14963cc84b48a11e69e4506b6.tar.bz2 linux-stable-3a373e027d8b0ed14963cc84b48a11e69e4506b6.zip |
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 'scripts/coccinelle/misc/orplus.cocci')
0 files changed, 0 insertions, 0 deletions