From: "andrzej zaborowski" <balrogg@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Carsten Otte <cotte@de.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH][RFC] Split non-TCG bits out of exec.c
Date: Fri, 14 Nov 2008 14:45:05 +0100 [thread overview]
Message-ID: <fb249edb0811140545y55bd84dfoc8f39f6ba3276f4f@mail.gmail.com> (raw)
In-Reply-To: <491CEE16.9040904@codemonkey.ws>
2008/11/14 Anthony Liguori <anthony@codemonkey.ws>:
> The issue is not disabling TCG at runtime. That's easy enough. The issue
> is that TCG doesn't exist (and probably won't ever exist) for certain
> architectures like ia64 and s390. Being forced to build with TCG support
> makes having QEMU + KVM not possible on these platforms even though they
> both support KVM.
I mean either compile-time or run-time: assuming that each QEMUAccel
implementation is a bunch of files + a struct with pointers in the
common code, it should make turning on/off each emulator easy.
Cheers
next prev parent reply other threads:[~2008-11-14 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 22:10 [Qemu-devel] [PATCH][RFC] Split non-TCG bits out of exec.c Anthony Liguori
2008-11-12 22:48 ` Fabrice Bellard
2008-11-12 22:53 ` Anthony Liguori
2008-11-13 13:51 ` andrzej zaborowski
2008-11-13 16:18 ` Anthony Liguori
2008-11-14 3:12 ` andrzej zaborowski
2008-11-14 3:18 ` Anthony Liguori
2008-11-14 13:45 ` andrzej zaborowski [this message]
2008-11-14 4:03 ` Jamie Lokier
2008-11-14 9:58 ` Avi Kivity
2008-11-14 13:23 ` Jamie Lokier
2008-11-16 13:07 ` Avi Kivity
2008-11-17 3:57 ` Jamie Lokier
2008-11-14 13:58 ` Anthony Liguori
2008-11-14 14:07 ` Anthony Liguori
2008-11-14 23:13 ` Jamie Lokier
2008-11-14 23:20 ` 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=fb249edb0811140545y55bd84dfoc8f39f6ba3276f4f@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=cotte@de.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).