From: Jerone Young <jyoung5@us.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm <kvm@vger.kernel.org>,
kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>
Subject: Re: Latest qemu tcg breakage
Date: Mon, 09 Jun 2008 11:55:39 -0500 [thread overview]
Message-ID: <1213030539.6792.21.camel@thinkpadL> (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.
Hmm...this may just be what is needed. Building upstream CVS works.
Actually building without --disable-cpu-emulation WORKS.
So given this I'll create a patch to remove --disable-cpu-emulation and
the fake cpu-exec files we have.
>
> Regards,
>
> Anthony Liguori
>
> > Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
> >
> > diff --git a/qemu/Makefile.target b/qemu/Makefile.target
> > --- a/qemu/Makefile.target
> > +++ b/qemu/Makefile.target
> > @@ -196,7 +196,6 @@ LIBOBJS+=fake-exec.o
> > LIBOBJS+=fake-exec.o
> > else
> > LIBOBJS+= translate-all.o translate.o
> > -endif
> > ifdef CONFIG_DYNGEN_OP
> > LIBOBJS+=op.o
> > endif
> > @@ -205,6 +204,7 @@ CPPFLAGS+=-I$(SRC_PATH)/tcg -I$(SRC_PATH
> > CPPFLAGS+=-I$(SRC_PATH)/tcg -I$(SRC_PATH)/tcg/$(ARCH)
> > ifeq ($(ARCH),sparc64)
> > CPPFLAGS+=-I$(SRC_PATH)/tcg/sparc
> > +endif
> > endif
> >
> > ifeq ($(USE_KVM), 1)
> > diff --git a/qemu/exec.c b/qemu/exec.c
> > --- a/qemu/exec.c
> > +++ b/qemu/exec.c
> > @@ -37,8 +37,11 @@
> > #include "exec-all.h"
> > #include "qemu-common.h"
> >
> > +#ifdef USE_KVM
> > +#include "qemu-kvm.h"
> > +#else
> > #include "tcg.h"
> > -#include "qemu-kvm.h"
> > +#endif
> >
> > #if defined(CONFIG_USER_ONLY)
> > #include <qemu.h>
> > @@ -3197,7 +3200,9 @@ void dump_exec_info(FILE *f,
> > cpu_fprintf(f, "TB flush count %d\n", tb_flush_count);
> > cpu_fprintf(f, "TB invalidate count %d\n",
> > tb_phys_invalidate_count);
> > cpu_fprintf(f, "TLB flush count %d\n", tlb_flush_count);
> > +#if !defined(USE_KVM)
> > tcg_dump_info(f, cpu_fprintf);
> > +#endif
> > }
> >
> > #if !defined(CONFIG_USER_ONLY)
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
next prev parent reply other threads:[~2008-06-09 16:55 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 [this message]
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
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=1213030539.6792.21.camel@thinkpadL \
--to=jyoung5@us.ibm.com \
--cc=anthony@codemonkey.ws \
--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