From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Latest qemu tcg breakage Date: Mon, 23 Jun 2008 21:33:31 -0500 Message-ID: <48605CFB.9040006@codemonkey.ws> References: <1213019621.6792.7.camel@thinkpadL> <484D5BBF.6030904@codemonkey.ws> <1214251581.18888.46.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: jyoung5@us.ibm.com, kvm , kvm-ppc-devel To: Hollis Blanchard Return-path: Received: from rv-out-0506.google.com ([209.85.198.230]:21879 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751265AbYFXCdv (ORCPT ); Mon, 23 Jun 2008 22:33:51 -0400 Received: by rv-out-0506.google.com with SMTP id k40so7389488rvb.1 for ; Mon, 23 Jun 2008 19:33:51 -0700 (PDT) In-Reply-To: <1214251581.18888.46.camel@localhost.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: Hollis Blanchard wrote: > On Mon, 2008-06-09 at 11:35 -0500, Anthony Liguori wrote: > =20 >> Jerone Young wrote: >> =20 >>> So upstream qemu is being pervasive about changes with TCG, startin= g to >>> place tcg only functions in exec.c . I've spun a quick patch that f= ixes >>> things for PowerPC when building qemu. But we need to try and isola= te >>> TCG in upstream qemu as it is starting to leak, and I'm not sure of= a >>> good way to fix it as there is no CONFIG defined for tcg currently= =2E >>> >>> Just something to keep in mind. >>> =20 >>> =20 >> Now that TCG supports PPC, shouldn't ya'll be able to drop=20 >> --disable-cpu-emulation. I believe that will simultaneously fix you= r=20 >> problem and reduce the difference between upstream QEMU. >> =20 > > Unfortunately, dropping =EF=BB=BF--disable-cpu-emulation would create= a gcc3 > dependency for us, which would suck. (Qemu still uses dyngen for > PowerPC, and it does still require gcc3.) > =20 But there's always been a GCC3 dependency. --disable-cpu-emulation was= =20 working around the breakage caused by TCG's introduction. That's been=20 fixed. Regards, Anthony Liguori