Quoting Nick Piggin <[email protected]>:
On Friday 07 December 2007 19:45, Ingo Molnar wrote:
ah, printk_clock() still uses sched_clock(), not jiffies. So it's not
the jiffies counter that goes back and forth, it's sched_clock() - so
this is a printk timestamps anomaly, not related to jiffies. I thought
we have fixed this bug in the printk code already: sched_clock() is a
'raw' interface that should not be used directly - the proper interface
is cpu_clock(cpu).
It's a single CPU box, so sched_clock() jumping would still be
problematic, no?
I guess so. Definitely, it didn't look like a printk issue. Drivers
don't read logs, usually. But they got confused anyway (it seems that
udelay's get scaled or fail or somesuch - I can't test it right now,
will provide more feedback in a few hours).
--
Ciao
Stefano
--
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
