xen/x86: don't lose event interrupts
authorStefano Stabellini <sstabellini@kernel.org>
Sat, 16 Apr 2016 01:23:00 +0000 (18:23 -0700)
committerJiri Slaby <jslaby@suse.cz>
Tue, 9 May 2017 06:19:52 +0000 (08:19 +0200)
commit97254930bc706c411f49084a7fc30123ab9fb099
treecdf7c240bb1b61af5852c7bcb71662e6283c7f34
parentbf7a633d28b46b79d293f0262d8eb701251833d0
xen/x86: don't lose event interrupts

commit c06b6d70feb32d28f04ba37aa3df17973fd37b6b upstream.

On slow platforms with unreliable TSC, such as QEMU emulated machines,
it is possible for the kernel to request the next event in the past. In
that case, in the current implementation of xen_vcpuop_clockevent, we
simply return -ETIME. To be precise the Xen returns -ETIME and we pass
it on. However the result of this is a missed event, which simply causes
the kernel to hang.

Instead it is better to always ask the hypervisor for a timer event,
even if the timeout is in the past. That way there are no lost
interrupts and the kernel survives. To do that, remove the
VCPU_SSHOTTMR_future flag.

Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
Acked-by: Juergen Gross <jgross@suse.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
arch/x86/xen/time.c