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: VMX changes for 6.16
Date: Fri, 23 May 2025 09:25:03 -0700	[thread overview]
Message-ID: <20250523162504.3281680-7-seanjc@google.com> (raw)
In-Reply-To: <20250523162504.3281680-1-seanjc@google.com>

A handful of minor tweaks and fixes, and a big reduction of the boilerplate
needed for forking vt_x86_ops between VMX and TDX.

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-vmx-6.16

for you to fetch changes up to 907092bf7cbddee4381729f23a33780d84b1bb7c:

  KVM: VMX: Clean up and macrofy x86_ops (2025-05-02 13:37:26 -0700)

----------------------------------------------------------------
KVM VMX changes for 6.16:

 - Explicitly check MSR load/store list counts to fix a potential overflow on
   32-bit kernels.

 - Flush shadow VMCSes on emergency reboot.

 - Revert mem_enc_ioctl() back to an optional hook, as it's nullified when
   SEV or TDX is disabled via Kconfig.

 - Macrofy the handling of vt_x86_ops to eliminate a pile of boilerplate code
   needed for TDX, and to optimize CONFIG_KVM_INTEL_TDX=n builds.

----------------------------------------------------------------
Chao Gao (1):
      KVM: VMX: Flush shadow VMCS on emergency reboot

Sean Christopherson (2):
      KVM: nVMX: Check MSR load/store list counts during VM-Enter consistency checks
      KVM: x86: Revert kvm_x86_ops.mem_enc_ioctl() back to an OPTIONAL hook

Uros Bizjak (1):
      KVM: VMX: Use LEAVE in vmx_do_interrupt_irqoff()

Vishal Verma (3):
      KVM: VMX: Move vt_apicv_pre_state_restore() to posted_intr.c and tweak name
      KVM: VMX: Define a VMX glue macro for kvm_complete_insn_gp()
      KVM: VMX: Clean up and macrofy x86_ops

 arch/x86/include/asm/kvm-x86-ops.h |   2 +-
 arch/x86/kvm/vmx/main.c            | 202 ++++++++++++++++++-------------------
 arch/x86/kvm/vmx/nested.c          |  31 ++++--
 arch/x86/kvm/vmx/posted_intr.c     |  10 +-
 arch/x86/kvm/vmx/posted_intr.h     |   3 +-
 arch/x86/kvm/vmx/vmenter.S         |   3 +-
 arch/x86/kvm/vmx/vmx.c             |   5 +-
 arch/x86/kvm/vmx/x86_ops.h         |  66 +-----------
 arch/x86/kvm/x86.c                 |   7 +-
 9 files changed, 142 insertions(+), 187 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 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
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 ` Sean Christopherson [this message]

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-7-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®