Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757357AbZKJRXv (ORCPT ); Tue, 10 Nov 2009 12:23:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755137AbZKJRXu (ORCPT ); Tue, 10 Nov 2009 12:23:50 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:51084 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754977AbZKJRXu (ORCPT ); Tue, 10 Nov 2009 12:23:50 -0500 Date: Tue, 10 Nov 2009 17:24:54 +0000 From: Alan Cox To: "H. Peter Anvin" Cc: Avi Kivity , Willy Tarreau , Pavel Machek , Matteo Croce , Sven-Haegar Koch , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: i686 quirk for AMD Geode Message-ID: <20091110172454.3c4481f2@lxorguk.ukuu.org.uk> In-Reply-To: <4AF99E04.8080704@zytor.com> References: <4AF4526B.4060101@zytor.com> <40101cc30911061418w357b74d8i3bf9a9537de052d4@mail.gmail.com> <20091108173708.GF1372@ucw.cz> <40101cc30911080940s18eb26bbg641beeaddbc25c3d@mail.gmail.com> <20091108181016.GB32364@elf.ucw.cz> <20091108193618.GB4186@elf.ucw.cz> <40101cc30911081147j77f7b81o86f2cc5a869aca1f@mail.gmail.com> <20091108195158.GD4186@elf.ucw.cz> <20091108200852.7f2cf092@lxorguk.ukuu.org.uk> <20091110052711.GA15338@1wt.eu> <4AF9020C.90108@zytor.com> <4AF9435F.2070103@redhat.com> <20091110105642.215804e0@lxorguk.ukuu.org.uk> <4AF99E04.8080704@zytor.com> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 952 Lines: 22 On Tue, 10 Nov 2009 09:08:20 -0800 "H. Peter Anvin" 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/