| 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
| ||
|
Date: Wed, 11 Jul 2007 15:51:39 -0700 From: Chris Wright <chrisw@...s-sol.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, Arjan van de Ven <arjan@...radead.org>, Chris Wright <chrisw@...s-sol.org> Subject: Re: x86 status was Re: -mm merge plans for 2.6.23 * Linus Torvalds (torvalds@...ux-foundation.org) wrote: > For example, we can make sure that the code in question that actually > touches the hardware stays exactly the same, and then just move the > interfaces around - and basically guarantee that _zero_ hardware-specific > issues pop up when you switch over, for example. That's not quite right. Leaving the code unchanged caused breakage already. The PIT is damn stupid and can be sensitive to how quickly it's programmed. So code that enable/disable didn't change, but frequency with which it is called did and broke some random boxes. > The other approach (which would be nice _too_) is to actually try to > convert one clock source at a time. Why is that not an option? It was that way for x86_64, that's the first thing I fixed (since it was done by fully disabling all other timers but the one coverted ;-) - 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