From: john stultz <johnstul@us.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC][PATCH -mm 1/2] i386: Detect clock skew during suspend
Date: Mon, 14 Aug 2006 12:58:47 -0700 [thread overview]
Message-ID: <1155585527.5413.56.camel@localhost.localdomain> (raw)
In-Reply-To: <200608132306.02079.rjw@sisk.pl>
On Sun, 2006-08-13 at 23:06 +0200, Rafael J. Wysocki wrote:
> Detect the situations in which the time after a resume from disk would
> be earlier than the time before the suspend and prevent them from
> happening on i386.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
One minor comment, but otherwise looks good.
> @@ -302,16 +305,25 @@ static int timer_resume(struct sys_devic
> {
> unsigned long flags;
> unsigned long sec;
> - unsigned long sleep_length;
> + unsigned long ctime = get_cmos_time();
> + long sleep_length = (ctime - sleep_start) * HZ;
> struct timespec ts;
> +
> + if (sleep_length < 0) {
> + printk(KERN_WARNING "Time skew detected in timer resume!\n");
Please make sure the warning describes the CMOS clock going backwards,
rather then just the vague "time skew detected" comment.
> + /* The time after the resume must not be earlier than the time
s/time/CMOS clock/
Acked-by: John Stultz <johnstul@us.ibm.com>
thanks
-john
next prev parent reply other threads:[~2006-08-14 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 21:02 [RFC][PATCH -mm 0/2] Detect clock skew during suspend Rafael J. Wysocki
2006-08-13 21:06 ` [RFC][PATCH -mm 1/2] i386: " Rafael J. Wysocki
2006-08-14 19:58 ` john stultz [this message]
2006-08-14 20:59 ` Rafael J. Wysocki
2006-08-13 21:07 ` [RFC][PATCH -mm 2/2] x86_64: " Rafael J. Wysocki
2006-08-14 18:15 ` Andi Kleen
2006-08-13 21:21 ` [RFC][PATCH -mm 0/2] " Pavel Machek
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=1155585527.5413.56.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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