From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SMP support
Date: Tue, 22 Nov 2005 20:23:05 +0100 [thread overview]
Message-ID: <43837019.5020408@bellard.org> (raw)
In-Reply-To: <1132673537.2569.10.camel@fred.ofc.soliddesign.net>
Joe Batt wrote:
> This
>
> qemu -smp 2 -cdrom KNOPPIX_V3.8-2005-02-28-CeBIT_Edition-qemu-0.6.1-2.iso
>
> fails, but work fine without the -smp flag. The KNOPPIX has fairly
> random seg faults. I had similar results with 4 virutal cpus.
>
> The host is a dual Xeon with hyperthreading turned on (so 4 total
> "CPUs") running Debian testing, and a custom 2.6.13 kernel. The
> compiler is gcc 3.3.5.
>
> You didn't offer up any description. Will this take advantage of host
> SMP? How? (Each of us could read the code, or you could save the
> collective a bunch of time...)
I will add some documentation soon. To be short: QEMU is still single
threaded which means that an SMP host does not increase the speed of an
SMP target. Each target CPU uses slots of 1 ms on the host. Currently
the performance is not optimal if "HLT" instructions are used on the
target CPUs (i.e. if some target CPUs are idle) but it will be improved
very soon. The QEMU accelerator is also not supported for SMP targets
(although it should work fine on SMP hosts).
For the future it could be possible to use host threads and to make the
QEMU accelerator target SMP aware but it is not my priority. I think it
is better to improve the correctness of the SMP target and to improve
the speed of the single threaded QEMU accelerator.
Fabrice.
next prev parent reply other threads:[~2005-11-22 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 0:00 [Qemu-devel] SMP support Fabrice Bellard
2005-11-22 4:19 ` Anthony Liguori
2005-11-22 4:46 ` Mulyadi Santosa
2005-11-22 15:32 ` Joe Batt
2005-11-22 19:23 ` Fabrice Bellard [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-25 12:57 Julio Guerra
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=43837019.5020408@bellard.org \
--to=fabrice@bellard.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).