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: Tue, 10 Nov 2009 17:24:54 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: "H. Peter Anvin" <hpa@...or.com> Cc: Avi Kivity <avi@...hat.com>, Willy Tarreau <w@....eu>, Pavel Machek <pavel@....cz>, Matteo Croce <technoboy85@...il.com>, Sven-Haegar Koch <haegar@...net.de>, Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org Subject: Re: i686 quirk for AMD Geode On Tue, 10 Nov 2009 09:08:20 -0800 "H. Peter Anvin" <hpa@...or.com> wrote: > On 11/10/2009 02:56 AM, Alan Cox wrote: > >> In theory yes. There would need to be a bit of work to disassociate it > >> from kvm, but nothing too difficult. > > > > For the tiny cases that actually matter using the KVM code appears a bit > > over the top. > > In the short term, yes, of course. However, if we're going to do > emulation, we might as well do it right. Why is using KVM doing it right ? It sounds like its doing it slowly, and hideously memory inefficiently. You are solving an uninteresting general case problem when you just need two tiny fixups (or perhaps 3 if you want to fix up early x86-64 prefetch) -- 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