From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 0/5] KVM: arm64: Some VGIC-related fixes
Date: Fri, 23 May 2025 18:35:39 +0100 [thread overview]
Message-ID: <87sekvdyc4.wl-maz@kernel.org> (raw)
In-Reply-To: <20250523160810.4049313-1-oliver.upton@linux.dev>
On Fri, 23 May 2025 17:08:05 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> Flushing out some patches I had sitting around before vacation:
>
> - The irqbypass hooks are not resilient to changes in the GSI<->MSI
> routing and can sometimes leave behind stale vLPI mappings for the
> VM. The fix is to resolve the VGIC IRQ using the host IRQ (which is
> stable) and nuking the vLPI mapping upon a routing change.
>
> - Closing another VGIC race where vCPU creation races with VGIC
> creation, leading to in-flight vCPUs entering the kernel w/o private
> IRQs allocated.
>
> Applies to kvmarm-6.16.
Apart from the couple of nits I mentioned in my reply to specific
patches, this looks good to me. If you can tidy it up some time before
-rc1, I'll happily queue it.
Thanks,
M.
--
Jazz isn't dead. It just smells funny.
prev parent reply other threads:[~2025-05-23 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 16:08 [PATCH 0/5] KVM: arm64: Some VGIC-related fixes Oliver Upton
2025-05-23 16:08 ` [PATCH 1/5] KVM: arm64: Use lock guard in vgic_v4_set_forwarding() Oliver Upton
2025-05-23 16:08 ` [PATCH 2/5] KVM: arm64: Protect vLPI translation with vgic_irq::irq_lock Oliver Upton
2025-05-23 16:08 ` [PATCH 3/5] KVM: arm64: Resolve vLPI by host IRQ in vgic_v4_unset_forwarding() Oliver Upton
2025-05-23 17:25 ` Marc Zyngier
2025-05-23 18:22 ` Oliver Upton
2025-05-23 16:08 ` [PATCH 4/5] KVM: arm64: Unmap vLPIs affected by changes to GSI routing information Oliver Upton
2025-05-23 17:26 ` Marc Zyngier
2025-05-23 17:48 ` Sean Christopherson
2025-05-23 18:14 ` Marc Zyngier
2025-05-23 20:54 ` Sean Christopherson
2025-05-23 20:58 ` Oliver Upton
2025-05-23 16:08 ` [PATCH 5/5] KVM: arm64: vgic-init: Plug vCPU vs. VGIC creation race Oliver Upton
2025-05-23 17:35 ` Marc Zyngier [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=87sekvdyc4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.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