From: Alexander Graf <agraf@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: mttcg@listserver.greensocs.com,
Mark Burton <mark.burton@greensocs.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Help on TLB Flush
Date: Thu, 12 Feb 2015 16:38:39 +0100 [thread overview]
Message-ID: <54DCC8FF.7000609@suse.de> (raw)
In-Reply-To: <CAFEAcA-YZMZPO_+AniZPpkryKyODwM=9DdzdDp6Wsda6BvegGw@mail.gmail.com>
On 12.02.15 15:58, Peter Maydell wrote:
> On 12 February 2015 at 14:45, Alexander Graf <agraf@suse.de> wrote:
>> almost nobody except x86 does global flushes
>
> All ARM TLB maintenance operations have both "this CPU only"
> and "all TLBs in the Inner Shareable domain" [that's ARM-speak
> for "every CPU core in the cluster"] variants (the latter
> being the TLB *IS operations). Looking at Linux's
> arch/arm64/mm/tlb.S and arch/arm64/include/asm/tlbflush.h
> most of the operations defined there use the IS variants.
Wow, did anyone benchmark this? I know that PPC switched away from
global flushes and instead tracks the CPUs a task was running on to
limit the scope of CPUs that need to flush.
Alex
next prev parent reply other threads:[~2015-02-12 15:38 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 [this message]
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
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=54DCC8FF.7000609@suse.de \
--to=agraf@suse.de \
--cc=mark.burton@greensocs.com \
--cc=mttcg@listserver.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.