From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <rth@twiddle.net>
Cc: "Emilio G. Cota" <cota@braap.org>,
Paolo Bonzini <pbonzini@redhat.com>,
MTTCG Devel <mttcg@greensocs.com>,
QEMU Developers <qemu-devel@nongnu.org>,
a.rigo@virtualopensystems.com,
Sergey Fedorov <serge.fdrv@gmail.com>,
Frederic Konrad <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] Making cputlb.c operations safe for MTTCG
Date: Wed, 28 Sep 2016 00:32:37 +0100 [thread overview]
Message-ID: <8737kkx6ju.fsf@linaro.org> (raw)
In-Reply-To: <d45d2659-fa70-f5ed-b92a-6338329d4535@twiddle.net>
Richard Henderson <rth@twiddle.net> writes:
> On 09/27/2016 03:29 PM, Emilio G. Cota wrote:
>> What's a quick-and-dirty way to disable the fast-path TLB lookups?
>> Alex: you told me the monitor has an option for this, but I can't
>> find it. I'm looking for something that'd go in tcg/i386 to simply
>> bypass the fast path.
>
> There is no easy way. If you need that, you'd have to significantly modify the
> tcg backend.
Surely all the backends force the slow-path when any of TLB_FLAGS_MASK
are set. Unless adding an extra bit is going to run out of spare bits on
some backends?
>
>
> r~
--
Alex Bennée
next prev parent reply other threads:[~2016-09-27 23:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 12:09 [Qemu-devel] Making cputlb.c operations safe for MTTCG Alex Bennée
2016-07-26 14:03 ` [Qemu-devel] [PATCH] cputlb: make tlb_reset_dirty " Alex Bennée
2016-08-01 14:54 ` [Qemu-devel] Making cputlb.c operations " Paolo Bonzini
2016-08-02 6:37 ` Alex Bennée
2016-08-02 10:26 ` Paolo Bonzini
2016-08-03 17:25 ` Richard Henderson
2016-08-03 20:56 ` Paolo Bonzini
2016-09-27 16:16 ` Paolo Bonzini
2016-09-27 22:15 ` Alex Bennée
2016-09-27 22:29 ` Emilio G. Cota
2016-09-27 23:04 ` Alex Bennée
2016-09-27 23:05 ` Richard Henderson
2016-09-27 23:32 ` Alex Bennée [this message]
2016-09-28 0:34 ` Richard Henderson
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=8737kkx6ju.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=a.rigo@virtualopensystems.com \
--cc=cota@braap.org \
--cc=fred.konrad@greensocs.com \
--cc=mttcg@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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 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.