xen: Remove clock_was_set() call in the resume path
authorDavid Vrabel <david.vrabel@citrix.com>
Thu, 27 Jun 2013 10:35:44 +0000 (11:35 +0100)
committerThomas Gleixner <tglx@linutronix.de>
Fri, 28 Jun 2013 21:15:06 +0000 (23:15 +0200)
commit 359cdd3f866(xen: maintain clock offset over save/restore) added
a clock_was_set() call into the xen resume code to propagate the
system time changes. With the modified hrtimer resume code, which
makes sure that all cpus are notified this call is not longer necessary.

[ tglx: Separated it from the hrtimer change ]

Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: John Stultz <john.stultz@linaro.org>
Cc: <xen-devel@lists.xen.org>
Link: http://lkml.kernel.org/r/1372329348-20841-2-git-send-email-david.vrabel@citrix.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
drivers/xen/manage.c

index 412b96cc5305746c20d554b1a6d2c7e55ab09686..421da856135d47cfbc889d0b4d0885b398d46c80 100644 (file)
@@ -166,9 +166,6 @@ out_resume:
 
        dpm_resume_end(si.cancelled ? PMSG_THAW : PMSG_RESTORE);
 
-       /* Make sure timer events get retriggered on all CPUs */
-       clock_was_set();
-
 out_thaw:
 #ifdef CONFIG_PREEMPT
        thaw_processes();