> They could be huge differences - unbounded, in fact. It would make > printk fairly hard to interpret, I would think. The only benefit to > using sched_clock in printk is that if you're using it to work out the > startup latencies you won't be confused by stolen time. But I think > that's a fairly small benefit compared to the disadvantage of not being > able to meaningfully compare the timestamps on two printk messages.
Ok so the right solution would be a separate printk_clock() that is implemented as the native sched_clock() even on Xen/VMI. Should be a SMOP. -Andi - 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/
