From: Tim Bird <tim.bird@am.sony.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Herbert Valerio Riedel <hvr@gnu.org>,
Clem Taylor <clem.taylor@gmail.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: CONFIG_PRINTK_TIME and initial value for jiffies?
Date: Mon, 22 May 2006 09:27:30 -0700 [thread overview]
Message-ID: <4471E672.6000907@am.sony.com> (raw)
In-Reply-To: <4469C71F.9060004@ru.mvista.com>
Sergei Shtylyov wrote:
> sched_clock() defined in arch/i386/kernel/timers/timer_tsc.c can
> hardly provide 0-based time if it's using TSC (at least I can't see
> where the TSC is cleared). Even if it's not using TSC, jiffies_64 is not
> 0-based as we saw, and neither it's set to -300 secs because of the
> double cast to ulong and then to u64 which should clear the high word.
> Probably something somewhere clears TSC but I can see the related code
> only in arch/i386/kernel/smpboot.c...
I've worked a lot with the printk_times feature, and it's not unusual
on many systems to see weird values before time_init(). On x86 with a
TSC-based sched_clock() you may see values based on whatever
the TSC happens to be after firmware initialization up until time_init().
Note that you can re-base the timings to an arbitrary printk line
using scripts/show_delta. See
http://tree.celinuxforum.org/CelfPubWiki/PrintkTimesSample2
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
prev parent reply other threads:[~2006-05-22 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 20:41 CONFIG_PRINTK_TIME and initial value for jiffies? Clem Taylor
2006-05-15 21:11 ` Sergei Shtylyov
2006-05-15 21:35 ` Sergei Shtylyov
2006-05-16 6:03 ` Herbert Valerio Riedel
2006-05-16 12:35 ` Sergei Shtylyov
2006-05-22 16:27 ` Tim Bird [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=4471E672.6000907@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=clem.taylor@gmail.com \
--cc=hvr@gnu.org \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.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