From: Avi Kivity <avi@qumranet.com>
To: jyoung5@us.ibm.com
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 19:15:05 +0300 [thread overview]
Message-ID: <484D5709.4000900@qumranet.com> (raw)
In-Reply-To: <1213019621.6792.7.camel@thinkpadL>
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.
>
>
> 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
>
We want to keep the ability to have both emulation (-no-kvm) and
virtualization, at least for x86, so let's keep tcg.h includable.
>
> #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
> }
>
>
How about
#define tcg_dump_info(x, y) (void)0
in some strategic spot?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-06-09 16:14 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 [this message]
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
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=484D5709.4000900@qumranet.com \
--to=avi@qumranet.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.