From: Will Deacon <will.deacon@arm.com>
To: Po-Yu Chuang <ratbert.chuang@gmail.com>
Cc: Sricharan R <r.sricharan@ti.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"nico@linaro.org" <nico@linaro.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: map_init_section flushes incorrect pmd
Date: Wed, 29 May 2013 09:54:27 +0100 [thread overview]
Message-ID: <20130529085426.GA13095@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CANutaR-2gTP7ubiEdgjFyzVMc6=4t5GPjLkH8pkup=O882Hb-Q@mail.gmail.com>
On Wed, May 29, 2013 at 03:14:58AM +0100, Po-Yu Chuang wrote:
> Will,
> I guess nobody noticed this because the MMU of later v7 processors
> fetches page table
> from D-cache. It even doesn't need to clean pmd to PoU.
It does if it's UP. The walker is only guaranteed to read from L1 if you
have the multiprocessing extensions.
As for this function, looks like it's ok because it has precisely one
caller, so it might be worth prefixing it with some underscores to make it
clear that nobody else should be calling it!
Will
next prev parent reply other threads:[~2013-05-29 8:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 10:48 Po-Yu Chuang
2013-05-28 13:05 ` Will Deacon
2013-05-28 14:03 ` Sricharan R
2013-05-28 14:07 ` Will Deacon
2013-05-28 18:48 ` Sricharan R
2013-05-29 2:14 ` Po-Yu Chuang
2013-05-29 8:54 ` Will Deacon [this message]
2013-05-29 9:34 ` Po-Yu Chuang
2013-05-30 8:15 ` Po-Yu Chuang
2013-05-30 9:12 ` Will Deacon
2013-05-30 11:33 ` Po-Yu Chuang
2013-05-30 11:46 ` [PATCH v2] " Po-Yu Chuang
2013-06-19 13:44 ` Jonas Jensen
2013-05-28 16:04 ` [PATCH] " Catalin Marinas
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=20130529085426.GA13095@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@linaro.org \
--cc=r.sricharan@ti.com \
--cc=ratbert.chuang@gmail.com \
--cc=rob.herring@calxeda.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
all inboxes | Powered by JetHome®