[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240510235055.2811352-4-seanjc@google.com>
Date: Fri, 10 May 2024 16:50:48 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Sean Christopherson <seanjc@...gle.com>
Subject: [GIT PULL] KVM: x86: MMU changes for 6.10
Tag says it all, though I feel the urge to have _something_ here.
The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:
Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-mmu-6.10
for you to fetch changes up to 226d9b8f16883ca412ef8efbad6f3594587a8dab:
KVM: x86/mmu: Fix a largely theoretical race in kvm_mmu_track_write() (2024-05-02 07:49:06 -0700)
----------------------------------------------------------------
KVM x86 MMU changes for 6.10:
- Process TDP MMU SPTEs that are are zapped while holding mmu_lock for read
after replacing REMOVED_SPTE with '0' and flushing remote TLBs, which allows
vCPU tasks to repopulate the zapped region while the zapper finishes tearing
down the old, defunct page tables.
- Fix a longstanding, likely benign-in-practice race where KVM could fail to
detect a write from kvm_mmu_track_write() to a shadowed GPTE if the GPTE is
first page table being shadowed.
----------------------------------------------------------------
David Matlack (1):
KVM: x86/mmu: Process atomically-zapped SPTEs after TLB flush
Sean Christopherson (1):
KVM: x86/mmu: Fix a largely theoretical race in kvm_mmu_track_write()
arch/x86/kvm/mmu/mmu.c | 20 +++++++++++--
arch/x86/kvm/mmu/tdp_mmu.c | 75 ++++++++++++++++++++++++++++++----------------
2 files changed, 66 insertions(+), 29 deletions(-)
Powered by blists - more mailing lists