From: Marc Zyngier <maz@kernel.org>
To: sascha.bischoff@googlemail.com,
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>, Joey Gouly <Joey.Gouly@arm.com>,
Suzuki Poulose <Suzuki.Poulose@arm.com>,
yuzenghui@huawei.com, will@kernel.org,
Oliver Upton <oupton@kernel.org>
Subject: Re: [PATCH 0/2] Enable GICv5 Legacy CPUIF trapping & fix TDIR cap test
Date: Tue, 27 Jan 2026 14:09:03 +0000 [thread overview]
Message-ID: <176952293346.2010102.7303410175644418702.b4-ty@kernel.org> (raw)
In-Reply-To: <20251208152724.3637157-2-sascha.bischoff@arm.com>
On Mon, 08 Dec 2025 15:28:22 +0000, Sascha Bischoff wrote:
> These changes address two trapping-related issues when running legacy
> (i.e. GICv3) guests on GICv5 hosts.
>
> The first change enables the vgic_v3_cpuif_trap static branch on GICv5
> hosts with legacy support, if trapping is required. The missing enable
> was caught as part of debugging why UNDEFs were being injected into
> guests when the ICH_HCR_EL2.TC bit was set - the expected bahaviour
> was that KVM should handle the trapped accesses, with the guest
> remaining blissfully unaware.
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: gic: Enable GICv3 CPUIF trapping on GICv5 hosts if required
commit: da63758c1876d899031066a9d4b8050af767ceb8
[2/2] KVM: arm64: Correct test for ICH_HCR_EL2_TDIR cap for GICv5 hosts
commit: 28e505d81766dcbe25c60d57ab9fc941cd3d38bf
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-01-27 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 15:28 Sascha Bischoff
2025-12-08 15:28 ` Sascha Bischoff
2026-01-27 14:09 ` Marc Zyngier [this message]
2025-12-08 15:28 ` [PATCH 1/2] KVM: arm64: gic: Enable GICv3 CPUIF trapping on GICv5 hosts if required Sascha Bischoff
2025-12-08 15:28 ` [PATCH 2/2] KVM: arm64: Correct test for ICH_HCR_EL2_TDIR cap for GICv5 hosts Sascha Bischoff
2025-12-08 15:53 ` [PATCH 0/2] Enable GICv5 Legacy CPUIF trapping & fix TDIR cap test Marc Zyngier
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=176952293346.2010102.7303410175644418702.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=oupton@kernel.org \
--cc=sascha.bischoff@googlemail.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®