Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754826Ab3CFHTL (ORCPT ); Wed, 6 Mar 2013 02:19:11 -0500 Received: from mga11.intel.com ([192.55.52.93]:37047 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754519Ab3CFHTI (ORCPT ); Wed, 6 Mar 2013 02:19:08 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,793,1355126400"; d="scan'208";a="299868770" From: Feng Tang To: Thomas Gleixner , John Stultz , Ingo Molnar , "H. Peter Anvin" , Jason Gunthorpe , x86@kernel.org, Len Brown , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org Cc: gong.chen@linux.intel.com, Feng Tang Subject: [PATCH v3 5/5] timekeeping: utilize the suspend-nonstop clocksource to count suspended time Date: Wed, 6 Mar 2013 15:17:51 +0800 Message-Id: <1362554271-22382-6-git-send-email-feng.tang@intel.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1362554271-22382-1-git-send-email-feng.tang@intel.com> References: <1362554271-22382-1-git-send-email-feng.tang@intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3260 Lines: 88 There are some new processors whose TSC clocksource won't stop during suspend. Currently, after system resumes, kernel will use persistent clock or RTC to compensate the sleep time, but for those new types of clocksources, we could skip the special compensation from external sources, and just use current clocksource for time recounting. This can solve some time drift bugs caused by some not-so-accurate or error-prone RTC devices. The current way to count suspened time is first try to use the persistent clock, and then try the rtc if persistent clock can't be used. This patch will change the trying order to: suspend-nonstop clocksource -> persistent clock -> rtc Signed-off-by: Feng Tang --- kernel/time/timekeeping.c | 42 ++++++++++++++++++++++++++++++++++-------- 1 file changed, 34 insertions(+), 8 deletions(-) diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c index 9a0bc98..bd7c27b 100644 --- a/kernel/time/timekeeping.c +++ b/kernel/time/timekeeping.c @@ -788,22 +788,48 @@ void timekeeping_inject_sleeptime(struct timespec *delta) static void timekeeping_resume(void) { struct timekeeper *tk = &timekeeper; + struct clocksource *clock = tk->clock; unsigned long flags; - struct timespec ts; + struct timespec ts_new, ts_delta; + cycle_t cycle_now, cycle_delta; + s64 nsec; - read_persistent_clock(&ts); + ts_delta.tv_sec = 0; + read_persistent_clock(&ts_new); clockevents_resume(); clocksource_resume(); write_seqlock_irqsave(&tk->lock, flags); - if (timespec_compare(&ts, &timekeeping_suspend_time) > 0) { - ts = timespec_sub(ts, timekeeping_suspend_time); - __timekeeping_inject_sleeptime(tk, &ts); - } - /* re-base the last cycle value */ - tk->clock->cycle_last = tk->clock->read(tk->clock); + /* + * After system resumes, we need to calculate the suspended time and + * compensate it for the OS time. There are 3 sources that could be + * used: Nonstop clocksource during suspend, persistent clock and rtc + * device. + * + * One specific platform may have 1 or 2 or all of them, and the + * preference will be: + * suspend-nonstop clocksource -> persistent clock -> rtc + * The less preferred source will only be tried if there is no better + * usable source. The rtc part is handled separately in rtc core code. + */ + cycle_now = clock->read(clock); + if ((clock->flags & CLOCK_SOURCE_SUSPEND_NONSTOP) && + cycle_now > clock->cycle_last) { + + cycle_delta = (cycle_now - clock->cycle_last) & clock->mask; + nsec = clocksource_cyc2ns(cycle_delta, clock->mult, + clock->shift); + ts_delta = ns_to_timespec(nsec); + } else if (timespec_compare(&ts_new, &timekeeping_suspend_time) > 0) + ts_delta = timespec_sub(ts_new, timekeeping_suspend_time); + + if (ts_delta.tv_sec >= 1) + __timekeeping_inject_sleeptime(tk, &ts_delta); + + /* Re-base the last cycle value */ + clock->cycle_last = clock->read(clock); tk->ntp_error = 0; timekeeping_suspended = 0; timekeeping_update(tk, false); -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/