From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: Cache issues in vexpress cpu shutdown (regression in 3.10)
Date: Thu, 6 Jun 2013 10:30:26 +0100 [thread overview]
Message-ID: <20130606093025.GC2650@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20130606092132.GB28479@arm.com>
On Thu, Jun 06, 2013 at 10:21:32AM +0100, Catalin Marinas wrote:
> On Wed, Jun 05, 2013 at 08:08:53PM +0100, Russell King - ARM Linux wrote:
> > On Wed, Jun 05, 2013 at 01:05:39PM +0100, Lorenzo Pieralisi wrote:
> > > There is an A9 errata (fixed in r1p0) whereby CLIDR[23:21] reads as 0
> > > where it should read as 3'b001, so basically flush_cache_louis is not
> > > flushing anything. If that's the problem, either we add a generic fix
> > > in v7 cache assembly or we just fix it in platform code (by calling
> > > flush_cache_all()), since there should not be many pre-r1p0 around.
> > >
> > > Please let me know what you think.
> >
> > If we're providing a flush_cache_louis() function, then it better do
> > what it says or be removed. So the right solution is to fix the
> > function rather than working around it, because over time we'll only
> > add more calls to flush_cache_louis() and it'll become a stumbling
> > block.
>
> I think at some point we should define this unification level in the DT,
> maybe together with the CPU topology. We use LoUIS because it seems to
> be the right thing on all the existing platforms but it's nothing in the
> architecture that says LoUIS is the right level of flushing for the
> CPU-local caches.
I definitely agree. For the time being, I am willing to patch the code
with an errata fix, waiting for the link between cache levels and
topology (and power domains) to get in the kernel.
Lorenzo
prev parent reply other threads:[~2013-06-06 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 11:09 Cache issues in vexpress cpu shutdown (regression in 3.10) Jon Medhurst (Tixy)
2013-06-05 11:39 ` Russell King - ARM Linux
2013-06-05 11:50 ` Will Deacon
2013-06-05 13:45 ` Jon Medhurst (Tixy)
2013-06-05 13:58 ` Will Deacon
2013-06-05 14:13 ` Pawel Moll
2013-06-05 12:05 ` Lorenzo Pieralisi
2013-06-05 19:08 ` Russell King - ARM Linux
2013-06-06 9:21 ` Catalin Marinas
2013-06-06 9:30 ` Lorenzo Pieralisi [this message]
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=20130606093025.GC2650@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).