On Fri, 16 Sep 2005, Tim Schmielau wrote:
> So, one jump (probably the first) happens when time_init sets use_tsc.
> Do we understand the other jump as well?
OK, looking at the numbers we have just one time-jump:
> [4294667.296000] CPU 0 irqstacks, hard=c03d2000 soft=c03d1000
> [4294667.296000] PID hash table entries: 2048 (order: 11, 32768 bytes)
> [ 0.000000] Detected 1400.279 MHz processor.
> [ 27.121583] Using tsc for high-res timesource
> [ 27.121620] Console: colour dummy device 80x25
> [ 27.122909] Dentry cache hash table entries: 131072 (order: 7, 524288
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.
So I think everything is well-understood. It's just a matter of whether
it's worth fixing.
Tim
-
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]
| |
 |