summaryrefslogtreecommitdiffstats
path: root/include/kvm
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2020-03-04 20:33:20 +0000
committerMarc Zyngier <maz@kernel.org>2020-03-24 12:15:51 +0000
commitae699ad348cdcd416cbf28e8a02fc468780161f7 (patch)
tree82593ec6caed02972b4c63e58bb22a11dcb663e2 /include/kvm
parent05d32df13c6b3c0850b68928048536e9a736d520 (diff)
downloadlinux-ae699ad348cdcd416cbf28e8a02fc468780161f7.tar.gz
linux-ae699ad348cdcd416cbf28e8a02fc468780161f7.tar.bz2
linux-ae699ad348cdcd416cbf28e8a02fc468780161f7.zip
irqchip/gic-v4.1: Move doorbell management to the GICv4 abstraction layer
In order to hide some of the differences between v4.0 and v4.1, move the doorbell management out of the KVM code, and into the GICv4-specific layer. This allows the calling code to ask for the doorbell when blocking, and otherwise to leave the doorbell permanently disabled. This matches the v4.1 code perfectly, and only results in a minor refactoring of the v4.0 code. Signed-off-by: Marc Zyngier <maz@kernel.org> Reviewed-by: Zenghui Yu <yuzenghui@huawei.com> Link: https://lore.kernel.org/r/20200304203330.4967-14-maz@kernel.org
Diffstat (limited to 'include/kvm')
-rw-r--r--include/kvm/arm_vgic.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/kvm/arm_vgic.h b/include/kvm/arm_vgic.h
index 9d53f545a3d5..63457908c9c4 100644
--- a/include/kvm/arm_vgic.h
+++ b/include/kvm/arm_vgic.h
@@ -70,6 +70,7 @@ struct vgic_global {
/* Hardware has GICv4? */
bool has_gicv4;
+ bool has_gicv4_1;
/* GIC system register CPU interface */
struct static_key_false gicv3_cpuif;