qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: andrzej zaborowski <balrogg@gmail.com>
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: Thu, 13 Nov 2008 21:18:46 -0600	[thread overview]
Message-ID: <491CEE16.9040904@codemonkey.ws> (raw)
In-Reply-To: <fb249edb0811131912y633e71f5o4850d54cd7956029@mail.gmail.com>

andrzej zaborowski wrote:
> 2008/11/13 Anthony Liguori <anthony@codemonkey.ws>:
>   
>> andrzej zaborowski wrote:
>>     
>>> Is this going a bit in the opposite direction to where QEMUAccel is
>>> going?  What Fabrice suggests seems to be like QEMUAccel, with TCG
>>> treated as another accelerator.
>>>
>>>       
>> QEMUAccel is a bit orthogonal to what I'm talking about.  There is already
>> KVM support in QEMU today and I'm merely looking to restructure existing
>> code so that I can build a version of QEMU that has no TCG support, only KVM
>> support.  TCG is too intimately woven into QEMU right now.  You could think
>> of this perhaps as a precursor to making TCG more of an "accelerator" than
>> it is today.
>>     
>
> Ah, I agree with your patch, I was only commenting on the idea of
> *-kvm/ targets.  I see something like QEMUAccel as a way to turn on
> and off the cpu emulators (TCG, kvm, kqemu).

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.

The idea behind a -kvm target is to be able to use QEMU + KVM on these 
architectures in a clean way.  We could also build qemu-system-s390 and 
just exclude TCG but from a naming perspective, it makes sense to be 
qemu-kvm because there can only be a single KVM executable for any given 
platform.

Regards,

Anthony Liguori

  reply	other threads:[~2008-11-14  3:18 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 [this message]
2008-11-14 13:45         ` andrzej zaborowski
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=491CEE16.9040904@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=balrogg@gmail.com \
    --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).