diff options
author | Christoffer Dall <christoffer.dall@linaro.org> | 2014-12-12 21:19:23 +0100 |
---|---|---|
committer | Christoffer Dall <christoffer.dall@linaro.org> | 2014-12-15 11:50:42 +0100 |
commit | 05971120fca43e0357789a14b3386bb56eef2201 (patch) | |
tree | e839f7efda57e1d53fa69c90315df4d0775716bf /Documentation/vm/hugetlbpage.txt | |
parent | arm/arm64: KVM: Initialize the vgic on-demand when injecting IRQs (diff) | |
download | linux-05971120fca43e0357789a14b3386bb56eef2201.tar.xz linux-05971120fca43e0357789a14b3386bb56eef2201.zip |
arm/arm64: KVM: Require in-kernel vgic for the arch timers
It is curently possible to run a VM with architected timers support
without creating an in-kernel VGIC, which will result in interrupts from
the virtual timer going nowhere.
To address this issue, move the architected timers initialization to the
time when we run a VCPU for the first time, and then only initialize
(and enable) the architected timers if we have a properly created and
initialized in-kernel VGIC.
When injecting interrupts from the virtual timer to the vgic, the
current setup should ensure that this never calls an on-demand init of
the VGIC, which is the only call path that could return an error from
kvm_vgic_inject_irq(), so capture the return value and raise a warning
if there's an error there.
We also change the kvm_timer_init() function from returning an int to be
a void function, since the function always succeeds.
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Diffstat (limited to 'Documentation/vm/hugetlbpage.txt')
0 files changed, 0 insertions, 0 deletions