Re: early printk timings way off

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tim Schmielau wrote:
> On Fri, 16 Sep 2005, Tim Schmielau wrote:
> The "Detected 1400.279 MHz processor." line just happens to be written
> _during_ time_init, when use_tsc is already set, but cycles_2_ns is not
> yet initialized.

That's exactly what I surmised as well.  Our e-mails must
have crossed each other.  :-)

> So I think everything is well-understood. It's just a matter of whether 
> it's worth fixing.

Exactly.  My own testing has focused on bootup time measurement.
Historically, the time spent before time_init() has been relatively
small and so I haven't (often) focused on trying to measure it
accurately.  Although, I have done this on occasion to get
complete results.

Andrew's suggestion of a replaceable clock function would
satisfy me.  What do other's think?

 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]
  Powered by Linux