public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Denys Fedoryshchenko <denys@visp.net.lb>,
	linux-kernel@vger.kernel.org
Subject: Re: strange timestamp in dmesg
Date: Fri, 6 Jun 2008 20:40:48 +0200	[thread overview]
Message-ID: <20080606184048.GB13101@one.firstfloor.org> (raw)
In-Reply-To: <20080606112547.13b78888.akpm@linux-foundation.org>

On Fri, Jun 06, 2008 at 11:25:47AM -0700, Andrew Morton wrote:
> We've seen a storm of hey-my-timestamps-went-weird reports in just the
> past month or so.  I don't recall it being (such) a problem before that.
> 
> Did we change something

Nominally not, but who really knows with 5 digit number worth of changesets?

At least 64bit should have been always like this, but you only
see it on specific circumstances.

> > I always advocated just always using jiffies for printk. The only drawback would
> > be that it won't increase in interrupt off sections, but if you have
> > one that is longer than a jiffie then you have enough other problems.
> 
> I forget why, but we _were_ going to have an (arch-overrideable)
> printk_clock() function.  And we still could.  The x86 implementation
> of that could fall back to jiffies if the TSCs are out of whack?

The rewritten sched_clock I used to plug, but which yielded about
zero interest, had one.

-Andi


      reply	other threads:[~2008-06-06 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 11:54 strange timestamp in dmesg Denys Fedoryshchenko
2008-06-06 10:19 ` Andrew Morton
2008-06-06 13:49   ` Andi Kleen
2008-06-06 18:25     ` Andrew Morton
2008-06-06 18:40       ` Andi Kleen [this message]

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=20080606184048.GB13101@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=denys@visp.net.lb \
    --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