LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alexey.zaytsev@gmail.com
Cc: mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: printk timestamps jumping back and forth in 2.6.25-rc.
Date: Thu, 28 Feb 2008 11:21:41 -0800 (PST)	[thread overview]
Message-ID: <20080228.112141.261415906.davem@davemloft.net> (raw)
In-Reply-To: <f19298770802280626g5ee17328ldedf7658a9f26f56@mail.gmail.com>

From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
Date: Thu, 28 Feb 2008 17:26:38 +0300

> commit d713f519332e029d43eca8462629314eee1ded86
> Author: Ingo Molnar <mingo@elte.hu>
> Date:   Fri Jan 25 21:07:58 2008 +0100
> 
>     sched: fix CONFIG_PRINT_TIME's reliance on sched_clock()
> 
>     Stefano Brivio reported weird printk timestamp behavior during
>     CPU frequency changes:
> 
>       http://bugzilla.kernel.org/show_bug.cgi?id=9475
> 
>     fix CONFIG_PRINT_TIME's reliance on sched_clock() and use cpu_clock()
>     instead.
> 
>     Reported-and-bisected-by: Stefano Brivio <stefano.brivio@polimi.it>
>     Signed-off-by: Ingo Molnar <mingo@elte.hu>
> 
> 
> which sound like "happy debugging, losers" to me. ;)
> 
> Anything else I can do?

FWIW, I've been seeing jumping printk timestamps ever since this
change on SMP sparc64 as well.  Especially on my Niagara boxes.

The timestamp base seem to be dependant upon which cpu prints the
message.  I guess the per-runqueue timestamps this new scheme is using
are all differently based.

  reply	other threads:[~2008-02-28 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 14:26 Alexey Zaytsev
2008-02-28 19:21 ` David Miller [this message]
2008-02-28 20:13 ` Ingo Molnar
2008-02-28 20:16   ` Ingo Molnar
2008-02-28 21:24     ` Alexey Zaytsev
2008-02-29 19:45       ` Ingo Molnar
2008-03-01  0:42         ` Alexey Zaytsev
2008-03-01  0:59           ` Alexey Zaytsev
2008-03-03 10:45             ` Ingo Molnar
2008-03-03 22:16               ` Alexey Zaytsev
2008-03-04 12:44                 ` Ingo Molnar
2008-02-29 11:11     ` Paul Mackerras
2008-02-29 18:42       ` David Miller
2008-02-29 19:44         ` Ingo Molnar
2008-03-21 18:55     ` Alexey Zaytsev

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=20080228.112141.261415906.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexey.zaytsev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --subject='Re: printk timestamps jumping back and forth in 2.6.25-rc.' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).