From: Oliver Upton <oupton@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Eric Auger <eric.auger@redhat.com>, Will Deacon <will@kernel.org>,
Fuad Tabba <tabba@google.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: arm64: vgic-v4: Don't allocate vPEs for a GICv2 VM
Date: Mon, 26 Oct 2026 14:30:09 -0700 [thread overview]
Message-ID: <at_GYZQr1RIUi2Tf@kernel.org> (raw)
In-Reply-To: <87qzhc8ce6.wl-maz@kernel.org>
On Mon, Oct 26, 2026 at 07:55:45PM +0000, Marc Zyngier wrote:
> On Mon, 26 Oct 2026 19:12:23 +0000,
> Oliver Upton <oupton@kernel.org> wrote:
> >
> > On Mon, Oct 26, 2026 at 03:26:38PM +0000, Fuad Tabba wrote:
> > > KVM can run a GICv2 VM on a GICv4.0 host whose CPU interface supports
> > > legacy operation.
> >
> > I'm pretty sure there's no IP out there that has GICv4.0 and legacy
> > mode...
>
> My favourite space heater, HiSi D05, says otherwise: 64 A72,
> GICv4.0. Remember that it is the *CPU* that provides compat mode, and
> not the GIC.
Well I forgot that one got glued together. Good thing you're on the hook
for fixes this round then ;)
Thanks,
Olier
next prev parent reply other threads:[~2026-10-26 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 15:26 [PATCH 0/2] KVM: arm64: vgic-v4: Don't allocate vPEs that a VM can't use Fuad Tabba
2026-10-26 15:26 ` [PATCH 1/2] KVM: arm64: vgic-v4: Don't allocate vPEs for a GICv2 VM Fuad Tabba
2026-10-26 19:12 ` Oliver Upton
2026-10-26 19:55 ` Marc Zyngier
2026-10-26 21:30 ` Oliver Upton [this message]
2026-10-27 7:37 ` Fuad Tabba
2026-10-26 15:26 ` [PATCH 2/2] KVM: arm64: vgic-v4: Don't allocate vPEs when userspace clears nASSGIcap Fuad Tabba
2026-10-26 19:39 ` Oliver Upton
2026-10-27 7:36 ` Fuad Tabba
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=at_GYZQr1RIUi2Tf@kernel.org \
--to=oupton@kernel.org \
--cc=eric.auger@redhat.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rananta@google.com \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--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
all inboxes | Powered by JetHome®