diff options
author | Sean Christopherson <seanjc@google.com> | 2024-10-10 11:23:34 -0700 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-10-25 12:58:00 -0400 |
commit | 7afe79f5734aebb55895424074bb944ac4717b7d (patch) | |
tree | 3fe536a99f1072dfdc4155a91d85b129c10347fe /fs | |
parent | 2bcb52a3602bf4cbc55d8fb4da00c930f83d7789 (diff) |
KVM: nVMX: Mark vmcs12's APIC access page dirty when unmapping
Mark the APIC access page as dirty when unmapping it from KVM. The fact
that the page _shouldn't_ be written doesn't guarantee the page _won't_ be
written. And while the contents are likely irrelevant, the values _are_
visible to the guest, i.e. dropping writes would be visible to the guest
(though obviously highly unlikely to be problematic in practice).
Marking the map dirty will allow specifying the write vs. read-only when
*mapping* the memory, which in turn will allow creating read-only maps.
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-33-seanjc@google.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions