From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
kvm-devel <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 3/3] Add KVM support to QEMU
Date: Tue, 28 Oct 2008 21:04:16 -0200 [thread overview]
Message-ID: <5d6222a80810281604g39708040kf710725dce6413dd@mail.gmail.com> (raw)
In-Reply-To: <49078955.2090109@codemonkey.ws>
On Tue, Oct 28, 2008 at 7:51 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Gerd Hoffmann wrote:
>>
>> Anthony Liguori wrote:
>>
>>>
>>> This patch only implements the bare minimum support to get a guest
>>> booting. It
>>> has very little impact the rest of QEMU and attempts to integrate nicely
>>> with
>>> the rest of QEMU.
>>>
>>
>> Huh? That isn't based on the qemu-accel patches ...
>>
>
> This is part of the reason for this exercise. I'd rather introduce KVM
> support first and then look at abstracting things, than vice versa. A
> number of the hooks in the current QEMUAccel tree are there for the wrong
> reason (to support the out-of-tree IO thread, for instance).
>
> If you just introduce something with various hooks and say, these are hooks
> we'll need, it's not possible to really evaluate whether the hooks are
> needed because nothing in the tree makes use of them.
We talked extensively on monday about it, and I'm in agreement with it.
>
> Regards,
>
> Anthony Liguori
>
>> surprised,
>> Gerd
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
>
>
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2008-10-28 23:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 20:13 [Qemu-devel] [PATCH 1/3] Add additional CPU flag definitions Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] [PATCH 2/3] Split CPUID from op_helper Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] [PATCH 3/3] Add KVM support to QEMU Anthony Liguori
2008-10-28 20:49 ` Hollis Blanchard
2008-10-28 21:10 ` Anthony Liguori
2008-10-28 20:57 ` Andreas Färber
2008-10-28 21:04 ` Glauber Costa
2008-10-28 21:16 ` Anthony Liguori
2008-10-28 21:05 ` Anthony Liguori
2008-11-04 13:25 ` Avi Kivity
2008-10-28 21:41 ` [Qemu-devel] " Gerd Hoffmann
2008-10-28 21:51 ` Anthony Liguori
2008-10-28 23:04 ` Glauber Costa [this message]
2008-10-28 23:36 ` Anthony Liguori
2008-10-29 9:54 ` Avi Kivity
2008-10-29 12:35 ` Glauber Costa
2008-10-29 12:39 ` Avi Kivity
2008-10-29 12:56 ` Glauber Costa
2008-10-29 13:07 ` Anthony Liguori
2008-10-29 13:23 ` Avi Kivity
2008-10-29 13:32 ` Anthony Liguori
2008-10-29 13:51 ` Hollis Blanchard
2008-10-29 14:09 ` Avi Kivity
2008-10-29 14:16 ` Fabrice Bellard
2008-10-29 14:23 ` Anthony Liguori
2008-10-29 19:13 ` Blue Swirl
2008-11-01 16:25 ` Blue Swirl
2008-10-29 14:58 ` Glauber Costa
2008-10-29 17:41 ` Glauber Costa
2008-10-29 19:01 ` Anthony Liguori
2008-11-04 13:24 ` Avi Kivity
2008-11-04 14:02 ` Anthony Liguori
2008-11-04 14:46 ` Avi Kivity
2008-11-04 14:50 ` 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=5d6222a80810281604g39708040kf710725dce6413dd@mail.gmail.com \
--to=glommer@gmail.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--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).