From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: MMU changes for 6.10
Date: Fri, 10 May 2024 16:50:48 -0700 [thread overview]
Message-ID: <20240510235055.2811352-4-seanjc@google.com> (raw)
In-Reply-To: <20240510235055.2811352-1-seanjc@google.com>
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(-)
next prev parent reply other threads:[~2024-05-10 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 23:50 KVM: x86 pull requests for 6.10 Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Common changes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-05-10 23:50 ` Sean Christopherson [this message]
2024-05-10 23:50 ` [GIT PULL] KVM: Selftests cleanups and fixes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Selftests "tree"-wide changes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2024-05-12 7:19 ` KVM: x86 pull requests " Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240510235055.2811352-4-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox