| To: | Clem Taylor <clem.taylor@gmail.com> |
|---|---|
| Subject: | Re: CONFIG_PRINTK_TIME and initial value for jiffies? |
| From: | Sergei Shtylyov <sshtylyov@ru.mvista.com> |
| Date: | Tue, 16 May 2006 01:35:11 +0400 |
| Cc: | Linux-MIPS <linux-mips@linux-mips.org> |
| In-reply-to: | <4468EE9B.4000009@ru.mvista.com> |
| Organization: | MontaVista Software Inc. |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <ecb4efd10605151341l33f491f1ueca8a0ce609c989d@mail.gmail.com> <4468EE9B.4000009@ru.mvista.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803 |
Sergei Shtylyov wrote: 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) Yes, the casting is weird. I somewat doubt that: #define INITIAL_JIFFIES ((unsigned long)(unsigned int) (-300*HZ)) u64 jiffies_64 = INITIAL_JIFFIES; can do the trick of wrapping around 5 mins after boot on x86... :-/ MBR, Sergei |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: CONFIG_PRINTK_TIME and initial value for jiffies?, Sergei Shtylyov |
|---|---|
| Next by Date: | Fwd: problem building cross compiler gcc-3.4.4, Shyamal Sadanshio |
| Previous by Thread: | Re: CONFIG_PRINTK_TIME and initial value for jiffies?, Sergei Shtylyov |
| Next by Thread: | Re: CONFIG_PRINTK_TIME and initial value for jiffies?, Herbert Valerio Riedel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |