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: SVM changes for 7.4
Date: Thu, 15 Oct 2026 21:44:12 -0700	[thread overview]
Message-ID: <20261016044415.958618-8-seanjc@google.com> (raw)
In-Reply-To: <20261016044415.958618-1-seanjc@google.com>

Not much this time around, mainly because PML and Bus Lock virtualization
support went in through the "misc" branch due to making significant changes
to common x86 code.

The following changes since commit d4b7fb647204f0c81dfeae2d1a708e4d858e0c94:

  Merge branch 'kvm-xen-longmode' into HEAD (2026-09-04 17:35:03 +0200)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-svm-7.4

for you to fetch changes up to 003892d6e802a1c08ad03e8ea793453465cae7f4:

  KVM: SEV: Return INVALID_INPUT on SNP req/resp buffer access failure (2026-09-28 17:55:11 -0700)

----------------------------------------------------------------
KVM SVM changes for 7.4

 - Fix a benign-in-practice bug where KVM unintentionally sets a non-zero
   error code when delivering exceptions to SEV-ES+ guests.

 - Force a new ASID in both VMCBs on pCPU migration to fix a bug where KVM can
   run a VMCB with a stale ASID due to the tracking being per-CPU, not per-VMCB.

 - Return INVALID_INPUT to the guest instead of exiting to userspace with -EIO
   if KVM can't access "guest request" buffer, i.e. try to keep the guest alive
   if the guest or userspace goofs.

----------------------------------------------------------------
Chaithanya Lagisetty (1):
      x86/svm: Avoid sign extension of SVM_EVTINJ_VALID in 64-bit expressions

Jacky Li (1):
      KVM: SEV: Return INVALID_INPUT on SNP req/resp buffer access failure

Yosry Ahmed (1):
      KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch

 arch/x86/include/asm/svm.h |  4 ++--
 arch/x86/kvm/svm/nested.c  |  1 +
 arch/x86/kvm/svm/sev.c     | 37 +++++++++++++++++++++++++++++++------
 arch/x86/kvm/svm/svm.c     | 19 +++++++++++++++----
 4 files changed, 49 insertions(+), 12 deletions(-)

  parent reply	other threads:[~2026-10-16  4:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  4:44 [GIT PULL] KVM: x86: Pull requests " Sean Christopherson
2026-10-16  4:44 ` [GIT PULL] KVM: x86: Timekeeping fixes+cleanups " Sean Christopherson
2026-10-16  4:44 ` [GIT PULL] KVM: guest_memfd and CoCo changes " Sean Christopherson
2026-10-16  4:44 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2026-10-16  4:44 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2026-10-16  4:44 ` [GIT PULL] KVM: selftests: Add PPC support Sean Christopherson
2026-10-16  4:44 ` [GIT PULL] KVM: Selftests changes for 7.4 Sean Christopherson
2026-10-16  4:44 ` Sean Christopherson [this message]
2026-10-16  4:44 ` [GIT PULL] KVM: x86: VMX+TDX " Sean Christopherson
2026-10-16  9:11 ` [GIT PULL] 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=20261016044415.958618-8-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®