From: Glauber Costa <glommer@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Main loop
Date: Mon, 28 Sep 2009 18:21:24 -0300 [thread overview]
Message-ID: <20090928212124.GP29735@mothafucka.localdomain> (raw)
In-Reply-To: <4AC10FFC.9070509@codemonkey.ws>
On Mon, Sep 28, 2009 at 02:35:24PM -0500, Anthony Liguori wrote:
> malc wrote:
>> Now that we have talked i see the problem and it basically boils down
>> to this: kvm can(and does) run multiple vcpus in multiple threads,
>> qemu always uses one, on top of this you are mainly interested in KVM
>> and i'm _only_ interested in TCG.
>
> The multiple vcpus in multiple threads model is the right one for TCG
> too. Both Paul and Fabrice have expressed interest in this in the past.
> For certain architecture combinations, it may not be that bad to
> implement either.
>
>> The way i see it the best approach
>> would be to factor out main loop into separate file and let QEMU and
>> KVM go their own separate ways w.r.t. this new entity.
>>
> OTOH, if most of the heavy lifting (like IO dispatch) can be refactored
> to shared functions, two main loops may not be so bad.
I am not opposed to it either.
next prev parent reply other threads:[~2009-09-28 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 23:55 [Qemu-devel] Main loop malc
2009-09-27 0:49 ` Anthony Liguori
2009-09-27 10:55 ` malc
2009-09-27 14:05 ` Anthony Liguori
2009-09-27 14:39 ` malc
2009-09-28 13:57 ` Glauber Costa
2009-09-28 18:50 ` malc
2009-09-28 19:35 ` Anthony Liguori
2009-09-28 21:21 ` Glauber Costa [this message]
2009-09-28 23:57 ` malc
2009-09-27 14:31 ` malc
2009-09-27 14:23 ` Blue Swirl
2009-09-27 14:35 ` malc
2009-09-27 17:43 ` malc
[not found] ` <m3fxa7jug0.fsf@neno.mitica>
2009-09-28 9:42 ` [Qemu-devel] " malc
[not found] ` <m3pr9bidy9.fsf@neno.mitica>
2009-09-28 10:19 ` malc
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=20090928212124.GP29735@mothafucka.localdomain \
--to=glommer@redhat.com \
--cc=anthony@codemonkey.ws \
--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).