From: Wenhao Xu <xuwenhao2008@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] multi-threaded smp support
Date: Wed, 20 Oct 2010 21:09:20 -0700 [thread overview]
Message-ID: <AANLkTim6P33UXZxFTBg9Z7E9mhNxpQyU5=OepV6ai3Uy@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
Hi, Folks,
AFAIK, QEMU supports SMP, but by using one thread to execute the
translated blocks of different CPU in an interleaving way. This makes the
SMP emulation very slow. I am wondering what are difficulties to use
multit-thread to emulate the SMP, e.g. using one thread to execute the
translated block of one CPU (core).
As as I can see, there are several difficulties (from a high level):
1. Dealing with global variables used by QEMU
2. Dealing with LOCK instructions
3. Dealing with other automatic memory update (setting page dirty bits)
I am interested in building this, but not sure about the potential
difficulties. Could anybody explain more on this? Thanks!
Wenhao
--
~_~
[-- Attachment #2: Type: text/html, Size: 766 bytes --]
next reply other threads:[~2010-10-21 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 4:09 Wenhao Xu [this message]
2010-10-21 5:47 ` [Qemu-devel] multi-threaded smp support Mulyadi Santosa
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='AANLkTim6P33UXZxFTBg9Z7E9mhNxpQyU5=OepV6ai3Uy@mail.gmail.com' \
--to=xuwenhao2008@gmail.com \
--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).