From: Frederic Konrad <fred.konrad@greensocs.com>
To: qemu-devel <qemu-devel@nongnu.org>, mttcg@listserver.greensocs.com
Subject: [Qemu-devel] TCG multithread plan.
Date: Mon, 08 Dec 2014 15:47:38 +0100 [thread overview]
Message-ID: <5485BA0A.4010206@greensocs.com> (raw)
Hi everybody,
Here is the plan we will follow:
We will be focusing - from the outset - on the end goal of multi-threaded TCG in full system emulation mode. On the way, we expect this will ‘fix’ user mode.
The plan is:
* Create one cache per CPU as a first step. We can do more next and share a cache.
* Update tb_* to add a pointer to their cache.
* Add atomic instruction support to the TGC (first on ARM).
* Make tb_invalidate work between all cache.
* Modify main-loop for multi-thread.
* Memory access (eg: for device) are not thread safe that need to be fixed. Initial plan simply globally mutex memory accesses - this may be optimised later.
* For now, irq handler for CPU seems ok but we need to check.
We will discuss this during the call tomorrow.
Thanks,
Fred
next reply other threads:[~2014-12-08 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 14:47 Frederic Konrad [this message]
2014-12-09 17:57 ` [Qemu-devel] TCG multithread plan Lluís Vilanova
2014-12-15 13:07 ` Mark Burton
2014-12-15 18:29 ` Lluís Vilanova
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=5485BA0A.4010206@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=mttcg@listserver.greensocs.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 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.