From: Hollis Blanchard <hollisb@us.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: jyoung5@us.ibm.com, kvm <kvm@vger.kernel.org>,
kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>
Subject: Re: Latest qemu tcg breakage
Date: Mon, 23 Jun 2008 15:06:21 -0500 [thread overview]
Message-ID: <1214251581.18888.46.camel@localhost.localdomain> (raw)
In-Reply-To: <484D5BBF.6030904@codemonkey.ws>
On Mon, 2008-06-09 at 11:35 -0500, Anthony Liguori wrote:
> Jerone Young wrote:
> > So upstream qemu is being pervasive about changes with TCG, starting to
> > place tcg only functions in exec.c . I've spun a quick patch that fixes
> > things for PowerPC when building qemu. But we need to try and isolate
> > 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.
> >
> > Just something to keep in mind.
> >
>
> Now that TCG supports PPC, shouldn't ya'll be able to drop
> --disable-cpu-emulation. I believe that will simultaneously fix your
> problem and reduce the difference between upstream QEMU.
Unfortunately, dropping --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.)
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-06-23 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 13:53 Latest qemu tcg breakage Jerone Young
2008-06-09 16:15 ` Avi Kivity
2008-06-09 16:35 ` Anthony Liguori
2008-06-09 16:55 ` Jerone Young
2008-06-09 20:51 ` Jerone Young
2008-06-09 21:02 ` Anthony Liguori
2008-06-09 21:09 ` Jerone Young
2008-06-23 20:06 ` Hollis Blanchard [this message]
2008-06-24 2:33 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1214251581.18888.46.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=jyoung5@us.ibm.com \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox