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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 8 Dec 2007 03:48:52 +1100 From: Nick Piggin <nickpiggin@...oo.com.au> To: Ingo Molnar <mingo@...e.hu> Cc: Stefano Brivio <stefano.brivio@...imi.it>, Robert Love <rml@...h9.net>, linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>, "Rafael J. Wysocki" <rjw@...k.pl>, Michael Buesch <mb@...sch.de>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org>, Len Brown <lenb@...nel.org> Subject: Re: [PATCH] scheduler: fix x86 regression in native_sched_clock On Friday 07 December 2007 22:17, Ingo Molnar wrote: > * Nick Piggin <nickpiggin@...oo.com.au> 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? > > sched_clock() is an internal API - the non-jumping API to be used by > printk is cpu_clock(). You know why sched_clock jumps when the TSC frequency changes, right? -- 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