diff options
| author | Christoffer Dall | 2017-05-16 19:53:50 +0200 |
|---|---|---|
| committer | Christoffer Dall | 2017-06-08 17:58:54 +0200 |
| commit | ebb127f2d6f32665643165289151bd20929d9931 (patch) | |
| tree | 4695b7aa5b5e3d1b126accc9bdba9c593d06ef4a /virt/kvm/arm/vgic/vgic-init.c | |
| parent | KVM: arm/arm64: Disallow userspace control of in-kernel IRQ lines (diff) | |
| download | kernel-qcow2-linux-ebb127f2d6f32665643165289151bd20929d9931.tar.gz kernel-qcow2-linux-ebb127f2d6f32665643165289151bd20929d9931.tar.xz kernel-qcow2-linux-ebb127f2d6f32665643165289151bd20929d9931.zip | |
KVM: arm/arm64: Don't assume initialized vgic when setting PMU IRQ
The PMU IRQ number is set through the VCPU device's KVM_SET_DEVICE_ATTR
ioctl handler for the KVM_ARM_VCPU_PMU_V3_IRQ attribute, but there is no
enforced or stated requirement that this must happen after initializing
the VGIC. As a result, calling vgic_valid_spi() which relies on the
nr_spis being set during the VGIC init can incorrectly fail.
Introduce irq_is_spi, which determines if an IRQ number is within the
SPI range without verifying it against the actual VGIC properties.
Signed-off-by: Christoffer Dall <cdall@linaro.org>
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt/kvm/arm/vgic/vgic-init.c')
0 files changed, 0 insertions, 0 deletions