From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Errata workaround updates
Date: Wed, 1 Feb 2012 16:33:06 +0000 [thread overview]
Message-ID: <20120201163306.GI3058@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1202011123420.2759@xanadu.home>
On Wed, Feb 01, 2012 at 04:26:18PM +0000, Nicolas Pitre wrote:
> On Wed, 1 Feb 2012, Will Deacon wrote:
>
> > Hello,
> >
> > After Russell pointed out that we weren't applying an erratum workaround
> > in all cases that it was required:
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-January/082730.html
> >
> > I went back through the documents for PL310 and Cortex-A9 to check that
> > what we have in Linux matches the latest workarounds.
>
> Ideally, you should not limit the workaround only to those revisions
> known to be broken but to any revision. Only when a particular revision
> is known to be fixed then should it be disabled.
For the general case I'd be inclined to agree, but when it involves poking
undocumented diagnostic registers I get scared and would rather only do it
when we know it's safe (since it could easily cause more problems on other
versions of the CPU).
Will
prev parent reply other threads:[~2012-02-01 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 13:52 [PATCH 0/2] Errata workaround updates Will Deacon
2012-02-01 13:52 ` [PATCH 1/2] ARM: errata: update workaround for A9 erratum #743622 Will Deacon
2012-02-01 13:52 ` [PATCH 2/2] ARM: errata: fix PL310 erratum #753970 workaround selection Will Deacon
2012-02-01 13:59 ` [PATCH 0/2] Errata workaround updates Shilimkar, Santosh
2012-02-01 16:26 ` Nicolas Pitre
2012-02-01 16:33 ` Will Deacon [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=20120201163306.GI3058@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 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).