From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"MTTCG Devel" <mttcg@greensocs.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Sergey Fedorov <serge.fdrv@gmail.com>,
.Cota@braap.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Should we introduce a TranslationRegion with its own codegen buffer?
Date: Mon, 4 Apr 2016 11:01:46 +0200 [thread overview]
Message-ID: <57022D7A.1040507@redhat.com> (raw)
In-Reply-To: <87y48tu53d.fsf@linaro.org>
On 04/04/2016 10:54, Alex Bennée wrote:
> Thoughts, objections? Discuss ;-)
I think we're putting a lot of carts before the horse.
We have like half a dozen subprojects and none are moving because
there's no clear idea of what to do next and why. The first thing to do
is to focus on fixing and speeding up user-mode MTTCG (Sergey's work on
upstreaming the patches from Fred and me) and on upstreaming Alvise's
work on ll/sc and TLB flushes.
The second thing to do is to make tb_flush thread safe; here there are
three competing mechanisms (Fred's run_safe_on_cpu, Emilio's mass
invalidation and my idea of using RCU) that we can discuss. Your idea
here is a fourth one. It's not a bad one, not at all. But even if it
has other positive side effects (e.g. easier jump patching), it's a
large project to embark on when there are at least three other
possibilities---two of them with code and the third (mine) being a
subset of yours.
Paolo
next prev parent reply other threads:[~2016-04-04 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:54 [Qemu-devel] Should we introduce a TranslationRegion with its own codegen buffer? Alex Bennée
2016-04-04 9:01 ` Paolo Bonzini [this message]
2016-04-04 10:39 ` Sergey Fedorov
2016-04-04 11:24 ` Alex Bennée
2016-04-04 11:33 ` Paolo Bonzini
2016-04-04 12:01 ` Alex Bennée
2016-04-04 12:13 ` Paolo Bonzini
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=57022D7A.1040507@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mttcg@greensocs.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=serge.fdrv@gmail.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).