From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [RFC] QEMU KVM target Date: Wed, 21 Feb 2007 10:34:43 +1100 Message-ID: <1172014483.24118.13.camel@localhost.localdomain> References: <45DA4A16.4050804@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Jun Koi Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Tue, 2007-02-20 at 11:55 +0900, Jun Koi wrote: > Howdy Anthony, > > > Here's a tiny patch that adds a i386-kvm target. The main difference > > between the i386-kvm and i386-softmmu target is that the -kvm target > > does not have any of the dyngen infrastructure. This means that it will > > build with gcc-4. I know you can do --cc=gcc to use gcc-4 but quite a > > few versions of gcc-4 have trouble with compiling dyngen. > > I understand that your approach is to remove the "binary translation" > part of the vanilla qemu, because we dont need it. We only need the > device emulation code of qemu for kvm. Do I understand correctly? > > If so, we do not need to depend on gcc3 tricks anymore. Removing the > dependent on gcc3 is really an important achievement. Does your patch still call the binary qemu? It'd be nice for distributions to have a real qemu still available as 'qemu', and the kvm-specific one as something else. Cheers, Rusty. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV