[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tip-0eb071651474952c8b6daecd36b378e2d01be22c@git.kernel.org>
Date: Fri, 28 Jun 2013 14:18:46 -0700
From: tip-bot for David Vrabel <tipbot@...or.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
konrad.wilk@...cle.com, john.stultz@...aro.org,
xen-devel@...ts.xen.org, tglx@...utronix.de,
david.vrabel@...rix.com
Subject: [tip:timers/core] xen: Remove clock_was_set()
call in the resume path
Commit-ID: 0eb071651474952c8b6daecd36b378e2d01be22c
Gitweb: http://git.kernel.org/tip/0eb071651474952c8b6daecd36b378e2d01be22c
Author: David Vrabel <david.vrabel@...rix.com>
AuthorDate: Thu, 27 Jun 2013 11:35:44 +0100
Committer: Thomas Gleixner <tglx@...utronix.de>
CommitDate: Fri, 28 Jun 2013 23:15:06 +0200
xen: Remove clock_was_set() call in the resume path
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@...rix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: John Stultz <john.stultz@...aro.org>
Cc: <xen-devel@...ts.xen.org>
Link: http://lkml.kernel.org/r/1372329348-20841-2-git-send-email-david.vrabel@citrix.com
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
---
drivers/xen/manage.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/xen/manage.c b/drivers/xen/manage.c
index 412b96c..421da85 100644
--- a/drivers/xen/manage.c
+++ b/drivers/xen/manage.c
@@ -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();
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists