public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Craig-Wood <ncw@axis.demon.co.uk>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Dan Kegel <dank@kegel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: time goes backwards periodically on laptop if booted in low-power mode
Date: Mon, 18 Feb 2002 22:12:14 +0000	[thread overview]
Message-ID: <20020218221214.A29199@axis.demon.co.uk> (raw)
In-Reply-To: <3C6FDB8C.9B033134@kegel.com> <20020218213049.A28604@axis.demon.co.uk> <3C71780F.6377F8D9@nortelnetworks.com>
In-Reply-To: <3C71780F.6377F8D9@nortelnetworks.com>; from cfriesen@nortelnetworks.com on Mon, Feb 18, 2002 at 04:54:23PM -0500

On Mon, Feb 18, 2002 at 04:54:23PM -0500, Chris Friesen wrote:
> Nick Craig-Wood wrote:
> > I made a patch to fix this (this is its first outing).  It stops
> > do_gettimeofday reporting a time less than it reported last time.
> 
> I see a minor problem here...what happens if you want to reset your clock (for
> whatever purpose) to a previous time?

Sorry that was a simplified explanation above.  If you examine the
patch you'll see that it can only change the time by < 1 jiffy (10ms).
However this is the interval wrongly estimated by the CPU's timer
(because the laptop's clock rate is not what the kernel thinks it is).

Ie, shouldn't be a problem.

-- 
Nick Craig-Wood
ncw@axis.demon.co.uk

  reply	other threads:[~2002-02-18 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-17 16:34 time goes backwards periodically on laptop if booted in low-power mode Dan Kegel
2002-02-18 21:30 ` Nick Craig-Wood
2002-02-18 21:50   ` Alan Cox
2002-02-18 21:56     ` Dan Kegel
2002-02-18 22:12       ` time goes backwards periodically on laptop if booted in low-power Alan Cox
2002-02-19  9:03     ` time goes backwards periodically on laptop if booted in low-power mode Nick Craig-Wood
2002-02-18 21:54   ` Chris Friesen
2002-02-18 22:12     ` Nick Craig-Wood [this message]
2002-02-18 23:06       ` Chris Friesen

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=20020218221214.A29199@axis.demon.co.uk \
    --to=ncw@axis.demon.co.uk \
    --cc=cfriesen@nortelnetworks.com \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.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