From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] RFC: ARM: cache-l2x0: update workaround for PL310 errata 727915
Date: Mon, 28 May 2012 11:11:32 +0100 [thread overview]
Message-ID: <20120528101132.GA956@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAMbhsRS_RtuvkrOh1nJ=cdYDgfM0tY9MivnbuWDcS_+NcW0qjQ@mail.gmail.com>
Hi Colin,
On Fri, May 25, 2012 at 09:04:22PM +0100, Colin Cross wrote:
> On Fri, May 25, 2012 at 7:56 AM, Will Deacon <will.deacon@arm.com> wrote:
> > Right, ok. This is definitely a different problem though. Firstly, r3p1 is
> > not affected by the original erratum and secondly the symptoms do not
> > include deadlock. The clean during boot also sounds highly suspicious -- is
> > there a chance you boot the kernel with a dirty L2? Is the L2 enabled or
> > disabled when entering the kernel [I think u8500 has it enabled]?
>
> In a previous thread, I wrote that the 4430 I was using had r2p0. I
> can't verify the accuracy of that claim right now, but my patch was
> based on that assumption. Where are you getting r3p1 from?
Apologies, that's what Santosh mentioned here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-May/101302.html
so, assuming that it's the same problem, it seems that both r3p1 and r2p0
are affected.
> When I said I couldn't reproduce the issue with clean during boot, I
> meant that I couldn't trigger the issue during boot by calling clean
> repeatedly. I could still reproduce the issue after boot even if the
> cache was cleaned during boot.
Ok, that's interesting. I wonder if erratum #769419 is to blame? We now have
a workaround in the kernel for that, so you could give it a try if you're in
a position to do so.
Cheers,
Will
next prev parent reply other threads:[~2012-05-28 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 20:41 [PATCH v2] RFC: ARM: cache-l2x0: update workaround for PL310 errata 727915 Linus Walleij
2012-05-21 6:04 ` Shilimkar, Santosh
2012-05-21 9:20 ` Linus Walleij
2012-05-21 9:23 ` Santosh Shilimkar
2012-05-22 8:52 ` Will Deacon
2012-05-22 9:22 ` Santosh Shilimkar
2012-05-22 9:34 ` Will Deacon
2012-05-22 18:36 ` Colin Cross
2012-05-25 14:56 ` Will Deacon
2012-05-25 20:04 ` Colin Cross
2012-05-28 10:11 ` Will Deacon [this message]
2012-05-28 10:17 ` Shilimkar, Santosh
2012-05-28 16:37 ` Colin Cross
2012-05-22 9:21 ` Will Deacon
2012-05-22 9:25 ` Linus Walleij
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=20120528101132.GA956@mudshark.cambridge.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 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.