summaryrefslogtreecommitdiffstats
path: root/arch/arm/xen
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2019-01-14 13:44:13 +0100
committerBoris Ostrovsky <boris.ostrovsky@oracle.com>2019-01-16 13:06:05 -0500
commit867cefb4cb1012f42cada1c7d1f35ac8dd276071 (patch)
tree2f343419e8513ee2cba477e262b4ba7fde507f03 /arch/arm/xen
parentb4711098066f1cf808d4dc11a1a842860a3292fe (diff)
downloadlinux-stable-867cefb4cb1012f42cada1c7d1f35ac8dd276071.tar.gz
linux-stable-867cefb4cb1012f42cada1c7d1f35ac8dd276071.tar.bz2
linux-stable-867cefb4cb1012f42cada1c7d1f35ac8dd276071.zip
xen: Fix x86 sched_clock() interface for xen
Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable' sched_clock() interface") broke Xen guest time handling across migration: [ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 187.251137] OOM killer disabled. [ 187.251137] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 187.252299] suspending xenstore... [ 187.266987] xen:grant_table: Grant tables using version 1 layout [18446743811.706476] OOM killer enabled. [18446743811.706478] Restarting tasks ... done. [18446743811.720505] Setting capacity to 16777216 Fix that by setting xen_sched_clock_offset at resume time to ensure a monotonic clock value. [boris: replaced pr_info() with pr_info_once() in xen_callback_vector() to avoid printing with incorrect timestamp during resume (as we haven't re-adjusted the clock yet)] Fixes: f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable' sched_clock() interface") Cc: <stable@vger.kernel.org> # 4.11 Reported-by: Hans van Kranenburg <hans.van.kranenburg@mendix.com> Signed-off-by: Juergen Gross <jgross@suse.com> Tested-by: Hans van Kranenburg <hans.van.kranenburg@mendix.com> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Diffstat (limited to 'arch/arm/xen')
0 files changed, 0 insertions, 0 deletions