| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080404144641.GA15844@elte.hu> Date: Fri, 4 Apr 2008 16:46:41 +0200 From: Ingo Molnar <mingo@...e.hu> To: Johannes Berg <johannes@...solutions.net> Cc: Benjamin Herrenschmidt <benh@...abs.org>, linuxppc-dev list <linuxppc-dev@...abs.org>, Arnd Bergmann <arndb@...ibm.com>, Linux Kernel list <linux-kernel@...r.kernel.org> Subject: Re: cpu_clock confusion (was: printk time confusion?) * Johannes Berg <johannes@...solutions.net> wrote: > Hi, > > > > Not sure whether the lockdep patches or something else is causing this > > > as I haven't checked w/o the patches yet, but I seem to be having some > > > confusion of printk timestamps: > > > > Tried reverting the patches ? > > That didn't help, so it's not the lockdep patches causing it. I'm still > seeing printk timestamps like this: > > [ 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 Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists