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 6.15-rc4
Date: Fri, 25 Apr 2025 12:29:27 -0400	[thread overview]
Message-ID: <20250425162927.404532-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit 8ffd015db85fea3e15a77027fda6c02ced4d2444:

  Linux 6.15-rc2 (2025-04-13 11:54:49 -0700)

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 2d7124941a273c7233849a7a2bbfbeb7e28f1caa:

  Merge tag 'kvmarm-fixes-6.15-2' of https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD (2025-04-24 13:28:53 -0400)

Compared to last week's botched attempt, this includes your suggestion
to make kvm_arch_has_irq_bypass() inline and a new ARM fix.

Paolo

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

* Single fix for broken usage of 'multi-MIDR' infrastructure in PI
  code, adding an open-coded erratum check for everyone's favorite pile
  of sand: Cavium ThunderX

x86:

* Bugfixes from a planned posted interrupt rework

* Do not use kvm_rip_read() unconditionally to cater for guests
  with inaccessible register state.

----------------------------------------------------------------
Adrian Hunter (2):
      KVM: x86: Do not use kvm_rip_read() unconditionally in KVM tracepoints
      KVM: x86: Do not use kvm_rip_read() unconditionally for KVM_PROFILING

Marc Zyngier (1):
      arm64: Rework checks for broken Cavium HW in the PI code

Paolo Bonzini (2):
      KVM: arm64, x86: make kvm_arch_has_irq_bypass() inline
      Merge tag 'kvmarm-fixes-6.15-2' of https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD

Sean Christopherson (8):
      KVM: SVM: Don't update IRTEs if APICv/AVIC is disabled
      KVM: SVM: Allocate IR data using atomic allocation
      KVM: x86: Reset IRTE to host control if *new* route isn't postable
      KVM: x86: Explicitly treat routing entry type changes as changes
      KVM: x86: Take irqfds.lock when adding/deleting IRQ bypass producer
      iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE
      iommu/amd: WARN if KVM attempts to set vCPU affinity without posted intrrupts
      KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added

 arch/arm64/include/asm/kvm_host.h |  5 +++
 arch/arm64/include/asm/mmu.h      | 11 -------
 arch/arm64/kernel/cpu_errata.c    |  2 +-
 arch/arm64/kernel/image-vars.h    |  4 ---
 arch/arm64/kernel/pi/map_kernel.c | 25 +++++++++++++-
 arch/arm64/kvm/arm.c              |  5 ---
 arch/x86/include/asm/kvm_host.h   |  6 ++++
 arch/x86/kvm/svm/avic.c           | 68 +++++++++++++++++++++------------------
 arch/x86/kvm/trace.h              | 13 ++++++--
 arch/x86/kvm/vmx/posted_intr.c    | 28 ++++++----------
 arch/x86/kvm/x86.c                | 28 ++++++++++------
 drivers/iommu/amd/iommu.c         | 15 +++------
 12 files changed, 116 insertions(+), 94 deletions(-)


             reply	other threads:[~2025-04-25 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 16:29 Paolo Bonzini [this message]
2025-04-25 19:45 ` 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=20250425162927.404532-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®