From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: erratum: Workaround for Kryo reserved system register read
Date: Tue, 12 Apr 2016 14:27:16 +0100 [thread overview]
Message-ID: <20160412132715.GC8066@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1460044456-5297-1-git-send-email-nkaje@codeaurora.org>
On Thu, Apr 07, 2016 at 09:54:16AM -0600, Naveen Kaje wrote:
> The ARMv8.0 architecture reserves several system register
> encodings for future use. These encodings should behave
> as read-only and always return zero on a read. The Kryo core
> errantly causes an instruction abort upon an AArch64
> read attempt to the following system register encodings using
> the MRS instruction:
> 3, 0, C0, [C4-C7], [2-3, 6-7]
> 3, 0, C0, C3, [3-7]
> 3, 0, C0, [C4,C6,C7], [4-5]
> 3, 0, C0, C2, [6-7]
> All system register encodings above use the following form
> Op0, Op1, CRn, CRm, Op2.
> Note that some of the encodings listed above include the system
> register space reserved for the following identification registers
> which may appear in future revisions of the ARM architecture beyond
> ARMv8.0.
Is this bug affecting test or production silicon? If the former (which I
presume is the case since such chip wouldn't have passed the ARM
validation suite), I won't merge the workaround into mainline. It is,
however, fine by me to give it to your early testers. We have a similar
approach with the ARM Ltd CPUs and don't upstream any CPU errata
workaround unless a partner goes with the silicon into production.
--
Catalin
prev parent reply other threads:[~2016-04-12 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:54 [PATCH] arm64: erratum: Workaround for Kryo reserved system register read Naveen Kaje
2016-04-07 17:31 ` Marc Zyngier
2016-04-08 9:58 ` Suzuki K Poulose
2016-04-08 10:24 ` Marc Zyngier
2016-04-08 10:31 ` Suzuki K Poulose
2016-04-08 11:00 ` Marc Zyngier
2016-04-11 6:49 ` James Morse
2016-04-11 10:06 ` Will Deacon
2016-04-12 13:27 ` Catalin Marinas [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=20160412132715.GC8066@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@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).