summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorSascha Bischoff <Sascha.Bischoff@arm.com>2026-09-04 11:35:48 +0000
committerMarc Zyngier <maz@kernel.org>2026-09-14 10:48:12 +0100
commit6055910efe9d5666eb096f5262e3501dbbca9aa2 (patch)
treec7d1537fb1dfc6ab5e9c2ec8c1dafdebee667685 /include/linux
parente6418104fbc661d5c9b280e5b9f3ff83709cf0c9 (diff)
downloadlinux-next-6055910efe9d5666eb096f5262e3501dbbca9aa2.tar.gz
linux-next-6055910efe9d5666eb096f5262e3501dbbca9aa2.zip
irqchip/gic-v5: Set up gic_kvm_info on ACPI hosts
Device-tree based GICv5 probing already passes the IRS details and maintenance interrupt to KVM, but the ACPI path only initialises the irqchip and installs the ACPI IRQ model. As a result, KVM never sees the GICv5 host information required to probe the vGIC on ACPI systems. Add the ACPI equivalent of the DT KVM setup. Parse the MADT GICC entries for the maintenance interrupt, retaining the value from the first relevant entry and warning if later entries disagree. Warn if firmware describes the interrupt as edge-triggered, but register it as a level-sensitive, active-high GSI. Pass the resulting IRQ together with the IRS base and coherency information to KVM. Native GICv5 does not require a maintenance interrupt unless the legacy GICv3-compatible CPU interface is present, so preserve the existing no-maintenance-IRQ handling for that case. Signed-off-by: Sascha Bischoff <sascha.bischoff@arm.com> Link: https://patch.msgid.link/20260904113404.4051341-4-sascha.bischoff@arm.com Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions