public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC] QEMU KVM target
Date: Mon, 19 Feb 2007 21:51:37 -0600	[thread overview]
Message-ID: <45DA7049.1050609@codemonkey.ws> (raw)
In-Reply-To: <fdaac4d50702191855gc2fc393ga83787bbf2d967da-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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?

Yup.

Regards,

Anthony Liguori

> If so, we do not need to depend on gcc3 tricks anymore. Removing the
> dependent on gcc3 is really an important achievement.
>
> Thanks,
> Jun
>


-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-02-20  3:51 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 [this message]
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
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=45DA7049.1050609@codemonkey.ws \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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