diff options
author | Alexander Graf <agraf@suse.de> | 2016-09-27 21:08:05 +0200 |
---|---|---|
committer | Christoffer Dall <cdall@linaro.org> | 2017-04-09 16:49:38 +0200 |
commit | 3fe17e6826162021d5e9274949571b19fc94826b (patch) | |
tree | c244b62d6c38003c7f453f8ba39a7cb3d0586c91 /virt/kvm/arm/arch_timer.c | |
parent | KVM: arm/arm64: Cleanup the arch timer code's irqchip checking (diff) | |
download | linux-3fe17e6826162021d5e9274949571b19fc94826b.tar.xz linux-3fe17e6826162021d5e9274949571b19fc94826b.zip |
KVM: arm/arm64: Add ARM user space interrupt signaling ABI
We have 2 modes for dealing with interrupts in the ARM world. We can
either handle them all using hardware acceleration through the vgic or
we can emulate a gic in user space and only drive CPU IRQ pins from
there.
Unfortunately, when driving IRQs from user space, we never tell user
space about events from devices emulated inside the kernel, which may
result in interrupt line state changes, so we lose out on for example
timer and PMU events if we run with user space gic emulation.
Define an ABI to publish such device output levels to userspace.
Reviewed-by: Alexander Graf <agraf@suse.de>
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt/kvm/arm/arch_timer.c')
0 files changed, 0 insertions, 0 deletions