diff options
| author |   Sean Christopherson <seanjc@google.com> | 2024-10-10 11:23:52 -0700 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2024-10-25 13:00:48 -0400 |
| commit | cb444acb697943c0aaeab085c43e07727cb0b85c (patch) | |
| tree | 2a4c546dced04a6f0cf2d624955fc2c664411a9c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | KVM: Move x86's API to release a faultin page to common KVM (diff) | |
| download | wireguard-linux-cb444acb697943c0aaeab085c43e07727cb0b85c.tar.xz wireguard-linux-cb444acb697943c0aaeab085c43e07727cb0b85c.zip | |
KVM: VMX: Hold mmu_lock until page is released when updating APIC access page
Hold mmu_lock across kvm_release_pfn_clean() when refreshing the APIC
access page address to ensure that KVM doesn't mark a page/folio as
accessed after it has been unmapped. Practically speaking marking a folio
accesses is benign in this scenario, as KVM does hold a reference (it's
really just marking folios dirty that is problematic), but there's no
reason not to be paranoid (moving the APIC access page isn't a hot path),
and no reason to be different from other mmu_notifier-protected flows in
KVM.
Tested-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Tested-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <20241010182427.1434605-51-seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions