[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aE-xyGGpHXdJ_pcF@linux.dev>
Date: Sun, 15 Jun 2025 22:55:20 -0700
From: Oliver Upton <oliver.upton@...ux.dev>
To: Wei-Lin Chang <r09922117@...e.ntu.edu.tw>
Cc: linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org, Marc Zyngier <maz@...nel.org>,
Joey Gouly <joey.gouly@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Jintack Lim <jintack@...columbia.edu>,
Christoffer Dall <christoffer.dall@....com>
Subject: Re: [PATCH] KVM: arm64: nv: Fix s_cpu_if->vgic_lr[] indexing in
vgic_v3_put_nested()
On Sat, Jun 14, 2025 at 10:57:21PM +0800, Wei-Lin Chang wrote:
> s_cpu_if->vgic_lr[] is filled continuously from index 0 to
> s_cpu_if->used_lrs - 1, but vgic_v3_put_nested() is indexing it using
> the positions of the set bits in shadow_if->lr_map. So correct it.
The changelog is a bit too mechanical and doesn't actually add anything
to the diff. Maybe:
Shadow LRs may exist at different indices from the corresponding LRs
in the guest hypervisor's vgic, as the shadow LRs are populated
contiguously in vgic_v3_create_shadow_lr().
Use the correct shadow LR index when forwarding vIRQ state back to the
guest hypervisor's vgic in vgic_v3_put_nested().
Diff itself LGTM.
Reviewed-by: Oliver Upton <oliver.upton@...ux.dev>
Thanks,
Oliver
Powered by blists - more mailing lists