From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Alvise Rigo <a.rigo@virtualopensystems.com>
Cc: mttcg@listserver.greensocs.com,
"Claudio Fontana" <claudio.fontana@huawei.com>,
"Mark Burton" <mark.burton@greensocs.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Jani Kokkonen" <jani.kokkonen@huawei.com>,
"tech@virtualopensystems.com" <tech@virtualopensystems.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] [mttcg] cputlb: Use async tlb_flush_by_mmuidx
Date: Mon, 29 Feb 2016 14:50:04 +0100 [thread overview]
Message-ID: <56D44C8C.3050800@redhat.com> (raw)
In-Reply-To: <CAFEAcA-q83jYc3atGjxRWuvEYXf3r6d8Q_wbYK4KCcuDj8Qi5g@mail.gmail.com>
On 29/02/2016 14:21, Peter Maydell wrote:
> On 29 February 2016 at 13:16, Alvise Rigo <a.rigo@virtualopensystems.com> wrote:
>> > As in the case of tlb_flush(), also tlb_flush_by_mmuidx has to query the
>> > TLB flush if it targets another VCPU. To accomplish this, a new async
>> > work has been added, together with a new TLBFlushByMMUIdxParams. A
>> > bitmap is used to track the MMU indexes to flush.
>> >
>> > This patch applies to the multi_tcg_v8 branch.
> What's the API for a target CPU emulation to say "and now I must
> wait for the TLB op to finish" before completing this guest
> instruction?
My proposal has been for a while for DMB to put the CPU in a halted
state (remote TLB callbacks then can decrement a counter and signal
cpu_halt_cond when it's zero), but no one has implemented this.
Paolo
next prev parent reply other threads:[~2016-02-29 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 13:16 [Qemu-devel] [mttcg] cputlb: Use async tlb_flush_by_mmuidx Alvise Rigo
2016-02-29 13:21 ` Peter Maydell
2016-02-29 13:50 ` Paolo Bonzini [this message]
2016-02-29 13:55 ` Peter Maydell
2016-02-29 14:02 ` alvise rigo
2016-02-29 14:06 ` Paolo Bonzini
2016-02-29 14:18 ` alvise rigo
2016-03-04 14:28 ` alvise rigo
2016-03-07 20:18 ` Alex Bennée
2016-03-07 21:18 ` Paolo Bonzini
2016-03-11 11:08 ` 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=56D44C8C.3050800@redhat.com \
--to=pbonzini@redhat.com \
--cc=a.rigo@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=claudio.fontana@huawei.com \
--cc=fred.konrad@greensocs.com \
--cc=jani.kokkonen@huawei.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--cc=peter.maydell@linaro.org \
--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 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.