From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC] QEMU KVM target
Date: Tue, 20 Feb 2007 18:17:08 -0600 [thread overview]
Message-ID: <45DB8F84.8040104@codemonkey.ws> (raw)
In-Reply-To: <1172014483.24118.13.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Rusty Russell wrote:
> On Tue, 2007-02-20 at 11:55 +0900, Jun Koi wrote:
>
>> Howdy Anthony,
>>
>>
>>> Here's a tiny patch that adds a i386-kvm target. The main difference
>>> between the i386-kvm and i386-softmmu target is that the -kvm target
>>> does not have any of the dyngen infrastructure. This means that it will
>>> build with gcc-4. I know you can do --cc=gcc to use gcc-4 but quite a
>>> few versions of gcc-4 have trouble with compiling dyngen.
>>>
>> I understand that your approach is to remove the "binary translation"
>> part of the vanilla qemu, because we dont need it. We only need the
>> device emulation code of qemu for kvm. Do I understand correctly?
>>
>> If so, we do not need to depend on gcc3 tricks anymore. Removing the
>> dependent on gcc3 is really an important achievement.
>>
>
> Does your patch still call the binary qemu? It'd be nice for
> distributions to have a real qemu still available as 'qemu', and the
> kvm-specific one as something else.
>
It calls it qemu-kvm (or qemu-system-x86_64-kvm). I'd like to find a
better name, perhaps qemu-system-i386-accel or something.
Regards,
Anthony Liguori
> Cheers,
> Rusty.
>
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-21 0:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 1:08 [RFC] QEMU KVM target Anthony Liguori
[not found] ` <45DA4A16.4050804-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-02-20 2:55 ` Jun Koi
[not found] ` <fdaac4d50702191855gc2fc393ga83787bbf2d967da-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-02-20 3:51 ` Anthony Liguori
2007-02-20 23:34 ` Rusty Russell
[not found] ` <1172014483.24118.13.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-02-21 0:17 ` Anthony Liguori [this message]
2007-02-20 7:19 ` Avi Kivity
[not found] ` <45DAA108.8000501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-20 9:48 ` Avi Kivity
[not found] ` <45DAC3FF.1090208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-20 15:19 ` Anthony Liguori
[not found] ` <45DB119A.8000809-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-02-20 15:21 ` Avi Kivity
[not found] ` <45DB11FD.1050900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-20 15:26 ` Anthony Liguori
[not found] ` <45DB1326.3060705-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-02-20 15:29 ` Avi Kivity
2007-02-20 15:13 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2007-02-20 9:44 Dylan Taft
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=45DB8F84.8040104@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.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