mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Tim Mann <mann@vmware.com>
Cc: linux-kernel@vger.kernel.org, mann@vmware.com, johnstul@us.ibm.com
Subject: Re: Fix time going backward with clock=pit [1/2]
Date: Thu, 18 May 2006 01:11:16 -0700	[thread overview]
Message-ID: <20060518011116.68055275.akpm@osdl.org> (raw)
In-Reply-To: <20060517160428.62022efd@mann-lx.eng.vmware.com>

Tim Mann <mann@vmware.com> wrote:
>
>  Currently, if you boot with clock=pit on the kernel command line and
>  run a program that loops calling gettimeofday, on many machines you'll
>  observe that time frequently goes backward by about one jiffy.  This
>  patch fixes that symptom and also some other related bugs.

It might be a bit late to get this into 2.6.17.  Although it does look
pretty safe and simple.  

Are many people hitting this problem?

And for 2.6.18 we're hoping to get John's x86 timer rework merged up. 
John, do those patches address this bug?

So if we decide these two patches are not-for-2.6.17 then I'll sit on them
until we decide whether or not to merge John's patches.  If we do, and if
those patches fix this problem then your two patches aren't needed.  If
John's patches don't get merged then I'll need to merge these two.

Hope that all makes sense ;)

  parent reply	other threads:[~2006-05-18  8:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 23:04 Tim Mann
2006-05-17 23:06 ` Fix time going backward with clock=pit [2/2] Tim Mann
2006-05-18  8:11 ` Andrew Morton [this message]
2006-05-19  1:54   ` Fix time going backward with clock=pit [1/2] Tim Mann
2006-05-26  0:09   ` [-mm PATCH] time: fix time going backward w/ clock=pit john stultz
2006-05-18 11:51 ` Fix time going backward with clock=pit [1/2] Roman Zippel
2006-05-18 18:50   ` Tim Mann
2006-05-19  0:09     ` Roman Zippel
2006-05-19  2:02       ` Tim Mann
2006-05-19 15:31         ` Roman Zippel
2006-05-19 23:13           ` Tim Mann

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=20060518011116.68055275.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mann@vmware.com \
    /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

all inboxes | Powered by JetHome®