mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM fixes for Linux 7.3-rc6
Date: Thu,  1 Oct 2026 13:22:14 -0400	[thread overview]
Message-ID: <20261001172214.209754-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit c2f24f140c2ee6c00775c2a93c6ac931acec2b60:

  Merge tag 'kvm-x86-fixes-7.3-rc5' of https://github.com/kvm-x86/linux into HEAD (2026-09-26 00:40:07 -0400)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus

for you to fetch changes up to f9bfc323e76120c2cd1fdea93bbf315eec5eb934:

  Merge tag 'kvmarm-fixes-7.3-2' of https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD (2026-10-01 13:13:57 -0400)

As mentioned in the previous PR, these are the patches that didn't make
it in time for rc5.  The most intrusive change is reverting a commit
from 7.3-rc1 that made struct kvm a bit too large, and fixing the same
issue otherwise.

There are again a lot of selftests lines; the sheer number of commits is
not small but I don't expect much more for 7.3 due to people travelling
to Plumbers next week.

----------------------------------------------------------------
ARM:

- Take a reference on the last IRQ loaded into an LR to prevent it
  from being freed while running the guest (Marc Zyngier)

- Ensure that the ITS MOVALL command only affects LPIs that were
  previously affined to the source redistributor (Marc Zyngier)

- Fix + test for honoring the host's trap configuration when running
  non-protected VMs while KVM is in protected mode (Fuad Tabba)

- Use the host stage-1 mapping granularity for VM_PFNMAP mappings at
  stage-2 (Mostafa Saleh)

x86:

Various bugfixes where the guest could do stupid things on purpose to
cause problems in the host:

- Failed VMRUNs can cause pending TLB flushes to be dropped, and in
  general some actions done through VMCB control fields have to be redone
  if VMRUN fails

- Toggling MSR interceptions or eVMCS execution controls can cause the
  host to use a stale MSR permission bitmap

- Bad page tables can cause a WARN.

Also fix issues in last week's pull request (my fault, for changing
email workflow and thus missing feedback sent to kvm@ but not LKML).

Generic:

- Take kvm_lock when creating vCPUs. For almost two decades everybody
  thought it was not done for some unspecified performance reasons, but
  in reality it was only done because kvm_lock was originally a spinlock.
  This is a better fix than 97d65b544f48 ("KVM: Check for duplicate vcpu_id
  as early as possible", from the 7.3 merge window), and does not waste
  2K per VM, hence its inclusion here.

----------------------------------------------------------------
Fuad Tabba (4):
      KVM: arm64: Apply the fine-grained UNDEFs without FEAT_FGT
      KVM: arm64: Clear HCR_EL2.RW for 32-bit non-protected vCPUs
      KVM: arm64: Use the host's HCR_EL2 for non-protected VMs in pKVM
      KVM: arm64: selftests: Check a feature hidden in an ID register is UNDEF

Marc Zyngier (3):
      KVM: arm64: vgic: Allow last_lr_irq to be NULL when LRs are not overflowing
      KVM: arm64: vgic: Take a refcount on IRQs referenced by last_lr_irq
      KVM: arm64: vgic-its: Fix MOVALL handling of source redistributor

Mostafa Saleh (1):
      KVM: arm64: Use stage-1 leaf size for VM_PFNMAP

Paolo Bonzini (1):
      Merge tag 'kvmarm-fixes-7.3-2' of https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD

Sean Christopherson (21):
      KVM: Reject attempts to lock all vCPUs if vCPU creation is in-progress
      KVM: arm64: vgic: Rely on vCPU creation check in "trylock all vCPUs"
      KVM: RISC-V: Use kvm_is_vcpu_creation_in_progress() instead of open-coded equivalent
      KVM: Protect all of kvm_vm_ioctl_create_vcpu() with kvm->lock
      KVM: Move check for existing vCPU ID to the top of vCPU creation
      Revert "KVM: Check for duplicate vcpu_id as early as possible"
      KVM: WARN if vCPU creation is in-progress when locking all vCPUs
      KVM: x86/mmu: Bail from shadow walks if the root is invalid or a dummy
      KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN
      KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded
      KVM: SVM: Don't mark ASID fields as dirty when setting control.tlb_ctl
      KVM: SVM: Sync guest's PERF_CNTR_GLOBAL_CTL from h/w only on successful VMRUN
      KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted
      KVM: nVMX: Force MSR bitmap refresh if runtime eVMCS controls are modified
      KVM: selftests: Add x2APIC MSR test for inhibiting APICv while nested
      KVM: selftests: Run the nested x2APIC with and without APICv being inhibited in L2
      KVM: selftests: Verify that L0's TPR doesn't get clobbered
      KVM: selftests: Extend nested x2APIC test to validate disabling x2APIC virt
      KVM: selftests: Extend nested x2APIC test to validate using eVMCS for vmcs12
      KVM: SEV: Nullify "have run CPUs" mask pointer when freeing it
      KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state

 arch/arm64/kvm/emulate-nested.c                    |   3 -
 arch/arm64/kvm/hyp/include/nvhe/pkvm.h             |   9 +
 arch/arm64/kvm/hyp/nvhe/hyp-main.c                 |   7 +-
 arch/arm64/kvm/hyp/nvhe/pkvm.c                     |  25 ++-
 arch/arm64/kvm/mmu.c                               |  47 +----
 arch/arm64/kvm/vgic/vgic-init.c                    |  12 +-
 arch/arm64/kvm/vgic/vgic-its.c                     |  12 +-
 arch/arm64/kvm/vgic/vgic-v2.c                      |   6 +-
 arch/arm64/kvm/vgic/vgic-v3.c                      |   6 +-
 arch/arm64/kvm/vgic/vgic.c                         |  21 +-
 arch/powerpc/kvm/book3s_hv.c                       |   2 -
 arch/riscv/kvm/aia_device.c                        |   2 +-
 arch/s390/kvm/s390/s390.c                          |   5 +-
 arch/x86/kvm/mmu/mmu.c                             |   6 +
 arch/x86/kvm/svm/sev.c                             |  57 +++---
 arch/x86/kvm/svm/svm.c                             |  43 ++--
 arch/x86/kvm/svm/svm.h                             |   1 +
 arch/x86/kvm/vmx/nested.c                          |   6 +
 arch/x86/kvm/vmx/tdx.c                             |   5 -
 include/linux/kvm_host.h                           |   1 -
 tools/testing/selftests/kvm/Makefile.kvm           |   2 +
 .../testing/selftests/kvm/arm64/hidden_features.c  | 184 +++++++++++++++++
 .../testing/selftests/kvm/x86/nested_x2apic_test.c | 222 +++++++++++++++++++++
 virt/kvm/kvm_main.c                                |  35 +---
 24 files changed, 554 insertions(+), 165 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/arm64/hidden_features.c
 create mode 100644 tools/testing/selftests/kvm/x86/nested_x2apic_test.c


             reply	other threads:[~2026-10-01 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 17:22 Paolo Bonzini [this message]
2026-10-01 21:37 ` pr-tracker-bot

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=20261001172214.209754-1-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®