From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Sascha Bischoff <Sascha.Bischoff@arm.com>
Cc: nd <nd@arm.com>,
oliver.upton@linux.dev, Joey Gouly <Joey.Gouly@arm.com>,
Suzuki Poulose <Suzuki.Poulose@arm.com>,
yuzenghui@huawei.com
Subject: Re: [PATCH] KVM: arm64: gic-v3: Only set ICH_HCR traps for v2-on-v3 or v3 guests
Date: Mon, 13 Oct 2025 17:56:15 +0100 [thread overview]
Message-ID: <176037441180.969330.798856280799815530.b4-ty@kernel.org> (raw)
In-Reply-To: <20251007160704.1673584-1-sascha.bischoff@arm.com>
On Tue, 07 Oct 2025 16:07:13 +0000, Sascha Bischoff wrote:
> The ICH_HCR_EL2 traps are used when running on GICv3 hardware, or when
> running a GICv3-based guest using FEAT_GCIE_LEGACY on GICv5
> hardware. When running a GICv2 guest on GICv3 hardware the traps are
> used to ensure that the guest never sees any part of GICv3 (only GICv2
> is visible to the guest), and when running a GICv3 guest they are used
> to trap in specific scenarios. They are not applicable for a
> GICv2-native guest, and won't be applicable for a(n upcoming) GICv5
> guest.
>
> [...]
Applied to fixes, thanks!
[1/1] KVM: arm64: gic-v3: Only set ICH_HCR traps for v2-on-v3 or v3 guests
commit: 3193287ddffbce29fd1a79d812f543c0fe4861d1
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-10-13 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 16:07 Sascha Bischoff
2025-10-13 16:56 ` Marc Zyngier [this message]
2025-10-21 0:21 ` Mark Brown
2025-10-21 0:50 ` Sean Christopherson
2025-10-21 11:39 ` Mark Brown
2025-10-21 7:50 ` Marc Zyngier
2025-10-21 14:00 ` Mark Brown
2025-10-21 14:37 ` Marc Zyngier
2025-10-21 18:47 ` Mark Brown
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=176037441180.969330.798856280799815530.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=Joey.Gouly@arm.com \
--cc=Sascha.Bischoff@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
--cc=oliver.upton@linux.dev \
--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®