From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Burton <mark.burton@greensocs.com>
Cc: mttcg@greensocs.com, Peter Maydell <peter.maydell@linaro.org>,
Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Help on TLB Flush
Date: Fri, 13 Feb 2015 10:49:04 +0100 [thread overview]
Message-ID: <54DDC890.4050801@redhat.com> (raw)
In-Reply-To: <B27AC2BA-62A7-42F6-B1DA-FDF96D44AB20@greensocs.com>
On 13/02/2015 10:37, Mark Burton wrote:
> the memory barrier is on the cpu requesting the flush isn’t it (not
> on the CPU that is being flushed)?
Oops, I misread Peter's explanation.
In that case, perhaps DMB can be treated in a similar way as WFI, using
cpu->halted. Queueing work on other CPUs can be done with
async_run_on_cpu, which exits the idle loop in qemu_tcg_wait_io_event
(this avoids the deadlocks). Checking that other CPUs have flushed the
TLBs can be done in cpu_has_work ("always return false if cpu->halted ==
true there are outstanding TLB requests").
Paolo
next prev parent reply other threads:[~2015-02-13 9:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 14:35 [Qemu-devel] Help on TLB Flush Mark Burton
2015-02-12 14:45 ` Alexander Graf
2015-02-12 14:58 ` Peter Maydell
2015-02-12 15:38 ` Alexander Graf
2015-02-12 16:02 ` Mark Burton
2015-02-12 22:10 ` Lluís Vilanova
2015-02-13 7:16 ` Mark Burton
2015-02-13 7:24 ` Peter Maydell
2015-02-13 7:37 ` Mark Burton
2015-02-13 13:30 ` Lluís Vilanova
2015-02-13 13:32 ` Mark Burton
2015-02-12 22:02 ` Peter Maydell
2015-02-12 15:01 ` Peter Maydell
2015-02-12 15:08 ` Mark Burton
2015-02-12 15:19 ` Alexander Graf
2015-02-12 21:57 ` Peter Maydell
2015-02-13 9:34 ` Paolo Bonzini
2015-02-13 9:37 ` Mark Burton
2015-02-13 9:49 ` Paolo Bonzini [this message]
2015-02-12 15:31 ` Dr. David Alan Gilbert
2015-02-12 18:44 ` Mark Burton
2015-02-12 15:11 ` Mark Burton
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=54DDC890.4050801@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=mark.burton@greensocs.com \
--cc=mttcg@greensocs.com \
--cc=peter.maydell@linaro.org \
--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 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.