]> git.proxmox.com Git - mirror_ubuntu-zesty-kernel.git/commit
xen/x86: don't lose event interrupts
authorStefano Stabellini <sstabellini@kernel.org>
Sat, 16 Apr 2016 01:23:00 +0000 (18:23 -0700)
committerThadeu Lima de Souza Cascardo <cascardo@canonical.com>
Fri, 5 May 2017 13:13:54 +0000 (10:13 -0300)
commitb25e16a350475ceea7b7aa6eca622ef03467adc1
tree5712eb177b7a68332e755f456ac21417b1e8f22b
parente294c5e0fd56bcb10aeedc03282a6ec514185cd5
xen/x86: don't lose event interrupts

BugLink: http://bugs.launchpad.net/bugs/1688505
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
arch/x86/xen/time.c