From: alvise rigo <a.rigo@virtualopensystems.com>
To: mttcg@listserver.greensocs.com
Cc: VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] TCG multithreaded
Date: Tue, 16 Dec 2014 14:09:59 +0100 [thread overview]
Message-ID: <CAH47eN2kknLk0Hz1mt5qna8ZM1bxbbnBJX3RLtc10D_E4hE9vQ@mail.gmail.com> (raw)
Hello,
Related to TCG multithreaded, at Virtual Open Systems, we have also
been working on it. More specifically we are looking on how to enable
a basic multithreaded vCPU infrastructure with one cache per CPU. We
intend to focus on the vCPU private tcg structures
(instantiation/initialization), as initial activity. As soon as we
have completed a first implementation, the plan is then to run
bare-metal test cases to verify basic thread functionality and
highlight future improvements (atomicity, tb invalidation, etc.).
Kind regards,
alvise
reply other threads:[~2014-12-16 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAH47eN2kknLk0Hz1mt5qna8ZM1bxbbnBJX3RLtc10D_E4hE9vQ@mail.gmail.com \
--to=a.rigo@virtualopensystems.com \
--cc=mttcg@listserver.greensocs.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
/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).