From: Feng Tang <feng.tang@intel.com>
To: Zoran Markovic <zoran.markovic@linaro.org>
Cc: linux-kernel@vger.kernel.org,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
stable@vger.kernel.org
Subject: Re: [RFC PATCH] timekeeping: Correct run-time detection of real-time clock.
Date: Sat, 12 Oct 2013 15:48:48 +0800 [thread overview]
Message-ID: <20131012074848.GA25366@feng-snb> (raw)
In-Reply-To: <1368815045-21209-1-git-send-email-zoran.markovic@linaro.org>
Hi Zoran,
Thanks for the patch! (This reply may be toooo late :))
One question just for curiosity: for the counter_32K timer, it's running
at 32K Hz and has one 32b counter. I understand it is only for suspend
time calculation use, but the wrap time for it is about
4G/32K ~= 128K seconds ~= 35 hours
What if one suspend time is longer than that?
- Feng
On Fri, May 17, 2013 at 11:24:05AM -0700, Zoran Markovic wrote:
> Since commit <31ade30692dc9680bfc95700d794818fa3f754ac>, timekeeping_init()
> checks for presence of persistent clock by attempting to read a non-zero
> time value from real-time clock. This is an issue on platforms where
> persistent_clock (instead of a RTC) is implemented as a free-running counter
> starting from zero on each boot and running during suspend. Examples are some
> ARM platforms (e.g. PandaBoard). An attempt to read such a clock during
> timekeeping_init() may return zero value and falsely declare persistent clock
> as missing. Additionally, in the above case suspend times may be accounted
> twice (once from timekeeping_resume() and once from rtc_resume()), resulting
> in a gradual drift of system time.
>
> This patch does a run-time correction of the issue by doing the same check
> during timekeeping_suspend().
>
> A better long-term solution would have to return error when trying to read
> non-existing clock and zero when trying to read an uninitialized clock, but
> that would require changing all persistent_clock implementations.
>
> This patch addresses the immediate breakage, for now.
>
> Cc: John Stultz <john.stultz@linaro.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Feng Tang <feng.tang@intel.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Zoran Markovic <zoran.markovic@linaro.org>
> ---
> kernel/time/timekeeping.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index 98cd470..baeeb5c 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -975,6 +975,14 @@ static int timekeeping_suspend(void)
>
> read_persistent_clock(&timekeeping_suspend_time);
>
> + /*
> + * On some systems the persistent_clock can not be detected at
> + * timekeeping_init by its return value, so if we see a valid
> + * value returned, update the persistent_clock_exists flag.
> + */
> + if (timekeeping_suspend_time.tv_sec || timekeeping_suspend_time.tv_nsec)
> + persistent_clock_exist = true;
> +
> raw_spin_lock_irqsave(&timekeeper_lock, flags);
> write_seqcount_begin(&timekeeper_seq);
> timekeeping_forward_now(tk);
> --
> 1.7.9.5
next prev parent reply other threads:[~2013-10-12 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 18:24 [RFC PATCH] timekeeping: Correct run-time detection of real-time clock Zoran Markovic
2013-05-17 18:39 ` John Stultz
2013-10-12 7:48 ` Feng Tang [this message]
2013-10-15 18:23 ` Zoran Markovic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131012074848.GA25366@feng-snb \
--to=feng.tang@intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zoran.markovic@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox