From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Valentine Burley <valentine.burley@collabora.com>,
Vincent Donnefort <vdonnefort@google.com>,
Joey Gouly <joey.gouly@arm.com>, Oliver Upton <oupton@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 7.0, take #3
Date: Wed, 11 Mar 2026 17:39:02 +0000 [thread overview]
Message-ID: <20260311173902.329537-1-maz@kernel.org> (raw)
Paolo,
Here's the third set of fixes for 7.0. Two fixes, both related to the
pretty large vgic rewrite that went into 6.19. One is affecting
interrupt deactivation, and therefore leading to guests locking
up. The other is affecting CPU hotplug with pKVM, leading to the
onlined CPU not booting at all.
Please pull,
M.
Marc Zyngier (2):
KVM: arm64: vgic: Pick EOIcount deactivations from AP-list tail
KVM: arm64: pkvm: Don't reprobe for ICH_VTR_EL2.TDS on CPU hotplug
arch/arm64/include/asm/kvm_host.h | 3 +++
arch/arm64/kernel/cpufeature.c | 9 +++++++++
arch/arm64/kvm/vgic/vgic-v2.c | 4 ++--
arch/arm64/kvm/vgic/vgic-v3.c | 12 ++++++------
arch/arm64/kvm/vgic/vgic.c | 6 ++++++
5 files changed, 26 insertions(+), 8 deletions(-)
--
2.47.3
The following changes since commit 3599c714c08c324f0fcfa392bfb857c92c575400:
KVM: arm64: Remove the redundant ISB in __kvm_at_s1e2() (2026-03-06 10:42:21 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-7.0-3
for you to fetch changes up to a79f7b4aeb8e7562cd6dbf9c223e2c2a04b1a85f:
KVM: arm64: pkvm: Don't reprobe for ICH_VTR_EL2.TDS on CPU hotplug (2026-03-10 09:48:45 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 7.0, take #3
- Correctly handle deeactivation of out-of-LRs interrupts by
starting the EOIcount deactivation walk *after* the last irq
that made it into an LR. This avoids deactivating irqs that
are in the LRs and that the vcpu hasn't deactivated yet.
- Avoid calling into the stubs to probe for ICH_VTR_EL2.TDS when
pKVM is already enabled -- not only thhis isn't possible (pKVM
will reject the call), but it is also useless: this can only
happen for a CPU that has already booted once, and the capability
will not change.
----------------------------------------------------------------
Marc Zyngier (2):
KVM: arm64: vgic: Pick EOIcount deactivations from AP-list tail
KVM: arm64: pkvm: Don't reprobe for ICH_VTR_EL2.TDS on CPU hotplug
arch/arm64/include/asm/kvm_host.h | 3 +++
arch/arm64/kernel/cpufeature.c | 9 +++++++++
arch/arm64/kvm/vgic/vgic-v2.c | 4 ++--
arch/arm64/kvm/vgic/vgic-v3.c | 12 ++++++------
arch/arm64/kvm/vgic/vgic.c | 6 ++++++
5 files changed, 26 insertions(+), 8 deletions(-)
next reply other threads:[~2026-03-11 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 17:39 Marc Zyngier [this message]
2026-03-11 17:42 ` [GIT PULL] KVM/arm64 fixes for 7.0, take #3 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=20260311173902.329537-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=valentine.burley@collabora.com \
--cc=vdonnefort@google.com \
--cc=yuzenghui@huawei.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