From: Paolo Bonzini <pbonzini@redhat.com>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
解壁伟 <xiebiwei@ict.ac.cn>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@gmail.com>
Subject: Re: [Qemu-devel] About the Thread model in Qemu【 Is it one thread per vcpu?】
Date: Wed, 13 Mar 2013 13:21:08 +0100 [thread overview]
Message-ID: <51406F34.40003@redhat.com> (raw)
In-Reply-To: <CABoDooOomgybLGgeQ=Fs=w5JFfLzFe0v6pzteOokygRhH4Qckg@mail.gmail.com>
Il 13/03/2013 10:56, Laurent Desnogues ha scritto:
>> > There has been some other research work with QEMU in this
>> > area, you should probably look it up. However it has all been
>> > "we fixed enough of the big problems to be able to run some
>> > benchmarks and write our research paper", so none of this is
>> > actually in the QEMU sources. (The short answer I think is
>> > "probably but it will depend a lot on workload, and there's
>> > a lot of software engineering required to do it reliably".)
> I know of two such variants: COREMU and HQEMU, but as far
> as I know the latter isn't freely available.
COREMU had one code generator per VCPU, if I remember correctly.
Jan Kiszka also posted an RFC patch that removed the "lockstep" behavior
of TCG, where the VCPU will always block the iothread even when it is
not executing MMIO. Getting this upstream would be an even bigger step
than making the code generator thread-safe.
Paolo
next prev parent reply other threads:[~2013-03-13 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:34 [Qemu-devel] About the Thread model in Qemu【 Is it one thread per vcpu?】 解壁伟
2013-03-12 22:26 ` Laszlo Ersek
2013-03-13 8:59 ` 解壁伟
2013-03-13 8:45 ` Stefan Hajnoczi
2013-03-13 9:32 ` 解壁伟
2013-03-13 9:51 ` Peter Maydell
2013-03-13 9:56 ` Laurent Desnogues
2013-03-13 12:21 ` Paolo Bonzini [this message]
2013-04-15 14:43 ` [Qemu-devel] Round robin of multi-vcpu in qemu 解壁伟
2013-04-23 1:25 ` 陳韋任 (Wei-Ren Chen)
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=51406F34.40003@redhat.com \
--to=pbonzini@redhat.com \
--cc=laurent.desnogues@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=xiebiwei@ict.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.