mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.16
Date: Fri, 23 May 2025 09:24:59 -0700	[thread overview]
Message-ID: <20250523162504.3281680-3-seanjc@google.com> (raw)
In-Reply-To: <20250523162504.3281680-1-seanjc@google.com>

Spurious fault cleanups, and minor fixup for S-EPT.

The following changes since commit 45eb29140e68ffe8e93a5471006858a018480a45:

  Merge branch 'kvm-fixes-6.15-rc4' into HEAD (2025-04-24 13:39:34 -0400)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-mmu-6.16

for you to fetch changes up to 6a3d704959bd04ab37fc588aff70b3078f3c90e8:

  KVM: x86/mmu: Use kvm_x86_call() instead of manual static_call() (2025-05-16 13:13:58 -0700)

----------------------------------------------------------------
KVM x86 MMU changes for 6.16:

 - Refine and harden handling of spurious faults.

 - Use kvm_x86_call() instead of open coding static_call().

----------------------------------------------------------------
Sean Christopherson (1):
      KVM: x86/mmu: Use kvm_x86_call() instead of manual static_call()

Yan Zhao (4):
      KVM: x86/mmu: Further check old SPTE is leaf for spurious prefetch fault
      KVM: x86/tdp_mmu: Merge prefetch and access checks for spurious faults
      KVM: x86/tdp_mmu: WARN if PFN changes for spurious faults
      KVM: x86/mmu: Warn if PFN changes on shadow-present SPTE in shadow MMU

 arch/x86/kvm/mmu/mmu.c     |  5 +++--
 arch/x86/kvm/mmu/tdp_mmu.c | 19 +++++++++----------
 2 files changed, 12 insertions(+), 12 deletions(-)

  parent reply	other threads:[~2025-05-23 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 16:24 [GIT PULL] KVM: x86: Changes " Sean Christopherson
2025-05-23 16:24 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2025-05-23 16:24 ` Sean Christopherson [this message]
2025-05-23 16:25 ` [GIT PULL] KVM: x86: Posted Interrupt PIR " Sean Christopherson
2025-05-23 16:25 ` [GIT PULL] KVM: selftests " Sean Christopherson
2025-05-23 16:25 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-05-23 16:25 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson

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=20250523162504.3281680-3-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

all inboxes | Powered by JetHome®