From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Clem Taylor <clem.taylor@gmail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: CONFIG_PRINTK_TIME and initial value for jiffies?
Date: Tue, 16 May 2006 01:11:55 +0400 [thread overview]
Message-ID: <4468EE9B.4000009@ru.mvista.com> (raw)
In-Reply-To: <ecb4efd10605151341l33f491f1ueca8a0ce609c989d@mail.gmail.com>
Hello.
Clem Taylor wrote:
> I just switched to 2.6.16.16 from 2.6.14 on a Au1550. I enabled
> CONFIG_PRINTK_TIME, and for some reason jiffies doesn't start out near
> zero like it does on x86. The first printk() always seems to have a
> time of 4284667.296000.
> jiffies_64 and wall_jiffies gets initialized to INITIAL_JIFFIES, but
> I'm not sure where jiffies is initialized. INITIAL_JIFFIES is -300*HZ
> (with some weird casting)
> The first line on the 2.6.16.16 Au1550 box is:
> [4294667.296000] Linux version 2.6.16.16 (ctaylor@gort) (gcc version
> 4.1.0) #4 Mon May 15 13:06:37 EDT 2006
Well, this number looks a lot like -300 secs printed as unsigned --
given the fact that jiffies are unsigned, there's no surprise...
My first guess is that TSC code used on x86 corrected jiffies_64 before
they got used by sched_clock(). Probably a bogus guess because TSC should have
been used by sched_clock() itsefl then...
MBR, Sergei
next prev parent reply other threads:[~2006-05-15 21:13 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 [this message]
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
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=4468EE9B.4000009@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=clem.taylor@gmail.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.