summaryrefslogtreecommitdiff
path: root/include/linux/irqchip
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2021-02-28 14:09:59 +0300
committerMarc Zyngier <maz@kernel.org>2021-06-01 12:45:59 +0300
commit669062d2a1aa36661b490683fe17810aa24a9cfb (patch)
tree88e24c9b60a2ab6890ed296fe012faba2a0f33bd /include/linux/irqchip
parent74501499d4e0d4ba59ab2bc6be1873716549169d (diff)
downloadlinux-669062d2a1aa36661b490683fe17810aa24a9cfb.tar.xz
KVM: arm64: vgic: Be tolerant to the lack of maintenance interrupt masking
As it turns out, not all the interrupt controllers are able to expose a vGIC maintenance interrupt that can be independently enabled/disabled. And to be fair, it doesn't really matter as all we require is for the interrupt to kick us out of guest mode out way or another. To that effect, add gic_kvm_info.no_maint_irq_mask for an interrupt controller to advertise the lack of masking. Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'include/linux/irqchip')
-rw-r--r--include/linux/irqchip/arm-vgic-info.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/irqchip/arm-vgic-info.h b/include/linux/irqchip/arm-vgic-info.h
index a25d4da5697d..7c0d08ebb82c 100644
--- a/include/linux/irqchip/arm-vgic-info.h
+++ b/include/linux/irqchip/arm-vgic-info.h
@@ -24,6 +24,8 @@ struct gic_kvm_info {
struct resource vcpu;
/* Interrupt number */
unsigned int maint_irq;
+ /* No interrupt mask, no need to use the above field */
+ bool no_maint_irq_mask;
/* Virtual control interface */
struct resource vctrl;
/* vlpi support */