From: Frederic Konrad <fred.konrad@greensocs.com>
To: qemu-devel <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
mttcg@greensocs.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Emilio G. Cota" <cota@braap.org>,
Mark Burton <mark.burton@greensocs.com>,
Guillaume Delbergue <guillaume.delbergue@greensocs.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: [Qemu-devel] MTTCG next version?
Date: Wed, 26 Aug 2015 14:18:24 +0200 [thread overview]
Message-ID: <55DDAE90.6090101@greensocs.com> (raw)
Hi everybody,
I'm trying to do the next version of the MTTCG work:
I would like to rebase on Alvise atomic instruction branch:
- Alvise can you rebase it on the 2.4.0 version without MTTCG support
and then
point me to the MTTCG specific changes so I can include them in my
tree?
I will add Paolo's linux-user and signal free qemu_cpu_kick series as well.
About tb_flush we think to do that without exiting:
- Use two buffers for tbs.
- Use a per tb invalidated flag.
- when tb_flush just invalidate all tb from the buffer and swap to
the second buffer:
VCPU which are executing code will discard their tb_jmp_cache when
they exit
(eg: run_on_cpu).
We need also to fix emulated data barrier so tlb_flush are finished
before the
instruction is executed. (That might be only data barrier breaks the TB).
Protecting page->code_bitmap and cpu_breakpoint_insert changes will be
squashed in the tb_lock patch.
More tests must be done especially with gdbstub and icount.
Do that make sense?
Fred
next reply other threads:[~2015-08-26 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 12:18 Frederic Konrad [this message]
2015-08-26 12:21 ` [Qemu-devel] MTTCG next version? Mark Burton
2015-08-26 15:07 ` Paolo Bonzini
2015-09-01 16:07 ` Alex Bennée
2015-08-26 18:34 ` Emilio G. Cota
2015-08-31 7:30 ` alvise rigo
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=55DDAE90.6090101@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=edgar.iglesias@gmail.com \
--cc=guillaume.delbergue@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@greensocs.com \
--cc=pbonzini@redhat.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).