> > [ 2.764009 (3/3)] > > [ 4.272241 (2/2)] > > [ 4.272322 (2/2)] > > [ 4.272375 (2/2)] > > [ 2.948002 (3/3)] > > > > As you can see, I added printk_cpu and smp_processor_id() to the > > printk timestamp output and thus it is obvious that the different > > times come from different CPUs. > > the fixes are queued for v2.6.26. You can pick them up from > sched-devel/latest as well: > > http://people.redhat.com/mingo/sched-devel.git/README
Hmm. Why is that whole cpu_clock stuff in place anyway? powerpc has perfectly synchronised time across processors with dirt cheap access to it as well, so why build all this code that only messes it up on top of it? johannes
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev