From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add flush_cache_vmap call in __early_set_fixmap
Date: Mon, 16 Jun 2014 15:17:17 +0100 [thread overview]
Message-ID: <20140616141717.GK16758@arm.com> (raw)
In-Reply-To: <20140609133859.GB18487@localhost>
On Mon, Jun 09, 2014 at 02:38:59PM +0100, Catalin Marinas wrote:
> On Mon, Jun 09, 2014 at 02:24:29PM +0100, Leif Lindholm wrote:
> > On Mon, Jun 09, 2014 at 12:03:56PM +0100, Catalin Marinas wrote:
> > > A quick grep through the kernel shows that we have other set_pte() calls
> > > without additional dsb() like create_mapping(), I think kvm_set_pte() as
> > > well.
> > >
> > > So I'm proposing an alternative patch (which needs some benchmarking as
> > > well to see if anything is affected, maybe application startup time).
> >
> > I'm happy for any fix which can be included in 3.16.
>
> Steve Capper made a point about performance. He'll follow up.
>
> > But is the dsb(ishst) sufficient? We need to also prevent reads from
> > overtaking the set_pte(). i.e.:
> >
> > ptr = early_ioremap(phys_addr, size);
> > if (ptr && strcmp(ptr, "magic") == 0)
> > ...
> >
> > Does it not require a dsb(ish)?
>
> So doesn't early_ioremap() now include a dsb() after set_pte() with my
> patch?
>
> BTW, according to the ARM ARM (and confirmed with architects), we needs
> DSB+ISB even if we have just a data access (rather than instruction
> fetch). We have to revisit both 32 and 64-bit code for this.
The impact of this really depends on whether or not we need to sandwich
DSB+ISB between every update to a set of page tables (possibly plumbing
together different levels) or whether the ISB can just come at the end.
If the latter case is true, we just need to add something for kernel
mappings, which should be pretty low overhead,
Will
next prev parent reply other threads:[~2014-06-16 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 10:29 [PATCH] arm64: Add flush_cache_vmap call in __early_set_fixmap Leif Lindholm
2014-06-06 14:37 ` Mark Salter
2014-06-06 14:53 ` Leif Lindholm
2014-06-06 15:09 ` Mark Salter
2014-06-09 11:03 ` Catalin Marinas
2014-06-09 13:24 ` Leif Lindholm
2014-06-09 13:38 ` Catalin Marinas
2014-06-09 16:40 ` Steve Capper
2014-06-10 10:39 ` Catalin Marinas
2014-06-16 14:17 ` Will Deacon [this message]
2014-06-16 14:12 ` Will Deacon
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=20140616141717.GK16758@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).