From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: L1 & L2 cache flush sequence on CortexA5 MPcore w.r.t low power modes
Date: Tue, 15 May 2012 11:09:02 +0100 [thread overview]
Message-ID: <20120515100902.GA10463@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20120515094010.GF10453@n2100.arm.linux.org.uk>
On Tue, May 15, 2012 at 10:40:10AM +0100, Russell King - ARM Linux wrote:
> On Mon, May 14, 2012 at 06:15:33PM +0100, Lorenzo Pieralisi wrote:
> > On Mon, May 14, 2012 at 05:39:09PM +0100, Russell King - ARM Linux wrote:
> > > From what you're saying - and from my understanding of your cache behaviours,
> > > even the sequence:
> > > - clean cache
> > > - disable C bit
> > > - clean cache
> > > is buggy.
> >
> > No, that's correct, works fine on A9 and A15. Second clean is mostly nops.
>
> It's racy. Consider this:
>
> - clean cache
> - cache speculatively prefetches a dirty cache line from another CPU
> - disable C bit
- clean cache
> At this point, you lose access to that dirty data. If that dirty data is
> used inbetween disabling the C bit and cleaning the cache for the second
> time, you have data corruption issues.
It is not racy. After disabling the C bit the cache clean operations write-back
any dirty cache line to the next cache level. And the CPU is still in coherency
mode so there is not a problem with that either.
> Another point which needs to be checked is whether dirty cache lines in
> a CPUs cache which has had the C bit disabled still take part in the
> coherency protocol with other CPUs. If the answer is no, then that's a
> _major_ problem for the hot unplug code paths. That effectively means
> that we have a window where a CPU going down actively _corrupts_ the
> data visible to other CPUs.
See above.
> As I have said, given what you've mentioned, it is impossible to safely
> disable the cache on a SMP system. In order to do it safely, you need to
> have a way to disable new allocations into the cache _without_ disabling
> the ability for the cache to be searched.
Cache lines can be acted upon with maintenance operations whether the C bit is
set or clear. For instance caches can be invalidated when the MMU is off
and the C bit is clear, eg v7 boot.
Cache cleaning and cache enabling/disabling are two different things, that's
valid for the PL310 as well.
Lorenzo
next prev parent reply other threads:[~2012-05-15 10:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 7:03 L1 & L2 cache flush sequence on CortexA5 MPcore w.r.t low power modes Murali N
2012-05-14 15:50 ` Lorenzo Pieralisi
2012-05-14 15:58 ` Russell King - ARM Linux
2012-05-14 16:21 ` Lorenzo Pieralisi
2012-05-14 16:39 ` Russell King - ARM Linux
2012-05-14 17:15 ` Lorenzo Pieralisi
2012-05-15 9:25 ` Murali N
2012-05-15 9:40 ` Russell King - ARM Linux
2012-05-15 10:09 ` Lorenzo Pieralisi [this message]
2012-05-15 10:15 ` Russell King - ARM Linux
2012-05-15 16:28 ` Lorenzo Pieralisi
2012-05-15 16:36 ` Russell King - ARM Linux
2012-05-15 17:05 ` Lorenzo Pieralisi
2012-09-19 8:55 ` Antti P Miettinen
2012-09-20 9:54 ` Lorenzo Pieralisi
2012-09-20 21:17 ` Antti P Miettinen
2012-09-23 21:32 ` Antti P Miettinen
2013-02-22 9:04 ` Antti P Miettinen
2013-02-22 9:39 ` Lorenzo Pieralisi
2013-02-23 20:41 ` Antti P Miettinen
2013-02-25 13:36 ` Lorenzo Pieralisi
2012-05-15 18:17 ` Will Deacon
2012-05-17 5:01 ` Murali N
2012-05-17 7:30 ` Shilimkar, Santosh
2013-12-24 17:52 ` Antti Miettinen
2014-01-06 12:43 ` Lorenzo Pieralisi
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=20120515100902.GA10463@e102568-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@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).