summaryrefslogtreecommitdiff
path: root/arch/sparc
diff options
context:
space:
mode:
authorStefano Stabellini <sstabellini@kernel.org>2016-04-15 18:23:00 -0700
committerSasha Levin <alexander.levin@verizon.com>2017-06-13 09:29:18 -0400
commit5023f12103b9185d89f484f7869cbdfb1059ae11 (patch)
tree1570717dc28b372b9c1de440750f47b5688e7e70 /arch/sparc
parentb64d082304fe242e9423f1a0dde540999de2dde2 (diff)
xen/x86: don't lose event interrupts
[ Upstream commit c06b6d70feb32d28f04ba37aa3df17973fd37b6b ] 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> Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Diffstat (limited to 'arch/sparc')
0 files changed, 0 insertions, 0 deletions