Make sure the timer test can properly handle a spurious timer interrupt, something that is far from being unlikely. Signed-off-by: Marc Zyngier <maz@xxxxxxxxxx> --- tools/testing/selftests/kvm/aarch64/arch_timer.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/testing/selftests/kvm/aarch64/arch_timer.c b/tools/testing/selftests/kvm/aarch64/arch_timer.c index 62af0e7d10b4..3f6f0bfa68a2 100644 --- a/tools/testing/selftests/kvm/aarch64/arch_timer.c +++ b/tools/testing/selftests/kvm/aarch64/arch_timer.c @@ -158,6 +158,9 @@ static void guest_irq_handler(struct ex_regs *regs) uint32_t cpu = guest_get_vcpuid(); struct test_vcpu_shared_data *shared_data = &vcpu_shared_data[cpu]; + if (intid == IAR_SPURIOUS) + return; + guest_validate_irq(intid, shared_data); WRITE_ONCE(shared_data->nr_iter, shared_data->nr_iter + 1); -- 2.34.1
