KVM: arm64: GICv2: Always trap GICV_DIR register

Browse source

Since we can't decide to trap the DIR register on a per-vcpu basis,
always trap the second page of the GIC CPU interface. Yes, this is
costly. On the bright side, no sane SW should use EOImode==1 on
GICv2...

Tested-by: Fuad Tabba <tabba@google.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Tested-by: Mark Brown <broonie@kernel.org>
Link: https://msgid.link/20251120172540.2267180-40-maz@kernel.org
Signed-off-by: Oliver Upton <oupton@kernel.org>

...

This commit is contained in:

Marc Zyngier 2025-11-20 17:25:29 +00:00 • committed by Oliver Upton

parent 255de897e7

commit 07bb1c5622

2 changed files with 5 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

arch/arm64/kvm/hyp/vgic-v2-cpuif-proxy.c

View file

2

arch/arm64/kvm/vgic/vgic-v2.c

View file