qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: mttcg@listserver.greensocs.com,
	"Claudio Fontana" <claudio.fontana@huawei.com>,
	"Mark Burton" <mark.burton@greensocs.com>,
	"Alvise Rigo" <a.rigo@virtualopensystems.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 13:55:26 +0000	[thread overview]
Message-ID: <CAFEAcA-igmLb61_wLhifg0qiT366mCEjDFw9vV7t1v2wgWdfAQ@mail.gmail.com> (raw)
In-Reply-To: <56D44C8C.3050800@redhat.com>

On 29 February 2016 at 13:50, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
> 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.

Yeah, that's the other approach -- really split the things that can
be async and do real "wait for completion" at points which must
synchronize. (Needs a little care since DMB is not the only such point.)
An initial implementation that does an immediate wait-for-completion
is probably simpler to review though, and add the real asynchrony
later. And either way you need an API for the target to wait for
completion.

thanks
-- PMM

  reply	other threads:[~2016-02-29 13:55 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
2016-02-29 13:55     ` Peter Maydell [this message]
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=CAFEAcA-igmLb61_wLhifg0qiT366mCEjDFw9vV7t1v2wgWdfAQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --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=pbonzini@redhat.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).