| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | CONFIG_PRINTK_TIME and initial value for jiffies? |
| From: | "Clem Taylor" <clem.taylor@gmail.com> |
| Date: | Mon, 15 May 2006 16:41:57 -0400 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MmhtGKmD3SryM0t8rHCOcO4T5Yswqy5et8Ho/P0yTGM95ViVVNQczLBu6yhZCBo07c3WiSplWfTx27LwJp8Q+ZFOfK7U7CXEH4r9uhRWrkb6CaTI9jRHLR/5eBWMx0ruiWgHUyHXPX0GQxD4tIp6t89ftm4pbS4n2R1ggXdWWVk= |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
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
The first line on a 2.6.16 x86_64 box is:
[ 0.000000] Bootdata ok (command line is ro root=/dev/md0)
[ 0.000000] Linux version 2.6.16 (ctaylor@klaatu) (gcc version
4.1.0 20060420 (Red Hat 4.1.0-9)) #3 SMP PREEMPT Sat Apr 29 03:36:06
EDT 2006
Shouldn't the first printk() have a time at or very near zero?
--Clem
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Qemu system shutdown support, Thiemo Seufer |
|---|---|
| Next by Date: | Re: CONFIG_PRINTK_TIME and initial value for jiffies?, Sergei Shtylyov |
| Previous by Thread: | [PATCH] fix interrupt handling for R2 CPUs, Thiemo Seufer |
| Next by Thread: | Re: CONFIG_PRINTK_TIME and initial value for jiffies?, Sergei Shtylyov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |