mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: john stultz <johnstul@us.ibm.com>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: Ktimer / -rt9 (+custom) monotonic_clock going backwards.
Date: Fri, 21 Oct 2005 02:03:13 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0510210157080.1946@localhost.localdomain> (raw)
In-Reply-To: <20051020193214.GA21613@elte.hu>


On Thu, 20 Oct 2005, Ingo Molnar wrote:

>
> * john stultz <johnstul@us.ibm.com> wrote:
>
> > > > John, would this cause any problems to keep cycle_t at s64?
> > >
> > > I mean at u64.
> >
> > Performance would be the only concern. It had been a u64 before I
> > started optimizing the code a bit.
>
> no, this is really a bad optimization that causes unrobustness.
> Correctness and robustness comes first. It is so easy to cause a
> 500-1000msec delay in the kernel, due to a bad driver or anything. The
> timekeeping code should not break like that.
>


FYI,

With rc4-rt13 and changing cycle_t to u64, my machine ran all night
without one backward step.  Since it use to show up after a couple of
hours, I would say that this is the fix.

John, Do you want me to take a crack at changing the periodic_hook into
using the ktimer code?  I understand Ingo's kernel much more than you, but
you definitely understand the timing code better than I.


Cheers,

-- Steve

  parent reply	other threads:[~2005-10-21  6:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 14:59 Steven Rostedt
2005-10-19 15:10 ` Thomas Gleixner
2005-10-19 18:39   ` john stultz
2005-10-20  6:55     ` Steven Rostedt
2005-10-20  7:34       ` Ingo Molnar
2005-10-20  7:46         ` Steven Rostedt
2005-10-20  8:01           ` Ingo Molnar
2005-10-20  8:56             ` Steven Rostedt
2005-10-20  8:59               ` Ingo Molnar
2005-10-20  9:04                 ` Steven Rostedt
2005-10-20  9:05                   ` Steven Rostedt
2005-10-20 10:05                   ` Steven Rostedt
2005-10-20 10:05                     ` Steven Rostedt
2005-10-20 15:55                       ` Ingo Molnar
2005-10-20 16:09                         ` Steven Rostedt
2005-10-20 16:45                       ` john stultz
2005-10-20 16:58                         ` Steven Rostedt
2005-10-20 17:05                           ` john stultz
2005-10-20 19:32                         ` Ingo Molnar
2005-10-20 20:05                           ` john stultz
2005-10-20 20:54                             ` Ingo Molnar
2005-10-21  6:03                           ` Steven Rostedt [this message]
2005-10-21  7:49                             ` Thomas Gleixner
2005-10-21  7:57                               ` Steven Rostedt
2005-10-21  8:00                               ` ktimer API Steven Rostedt
2005-10-21  8:09                                 ` Thomas Gleixner
2005-10-21 18:09                             ` Ktimer / -rt9 (+custom) monotonic_clock going backwards john stultz
2005-10-21 18:15                               ` Thomas Gleixner
2005-10-20 22:06           ` George Anzinger
2005-10-20  6:19   ` Steven Rostedt
2005-10-20 14:34   ` Steven Rostedt
2005-10-20 15:18     ` Steven Rostedt
2005-10-20 15:23       ` Steven Rostedt
2005-10-20 16:01       ` Steven Rostedt
2005-10-19 15:11 ` Ingo Molnar
2005-10-20  6:38   ` Steven Rostedt
2005-10-20  6:56     ` Ingo Molnar
2005-10-19 15:21 ` Daniel Walker
2005-10-20  6:39   ` Steven Rostedt
2005-10-20 15:02     ` Daniel Walker
2005-10-20 22:19       ` George Anzinger
2005-10-20 23:23         ` john stultz
2005-10-19 16:44 ` Frank Sorenson
2005-10-20  6:43   ` Steven Rostedt

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=Pine.LNX.4.58.0510210157080.1946@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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®