public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed

From: slash.tmp@free•fr (Mason)
To: linux-arm-kernel@lists•infradead.org
Subject: ERRATA work-arounds in the kernel
Date: Fri, 20 Mar 2015 17:30:10 +0100	[thread overview]
Message-ID: <550C4B12.1030608@free.fr> (raw)

Hello everyone,

I was recently looking (in arch/arm/Kconfig) at the list of work-arounds
for ARM CPU Errata. I saw 18, with 8 documented as applying to Cortex A9.

I also looked at ARM's "Errata Summary Table" for the Cortex A9. There are
roughly 90 errata documented there. (This document is 2 years old.)

I assume that some (most?) of these do not apply to Linux, but it seems
likely that some do?

I'm wondering why there are not more work-arounds available in Kconfig?

Could it be that some work-arounds have been applied unconditionally, thus
not showing as an entry in Kconfig? (I doubt that, since work-arounds are
very CPU-specific.)

I'm wondering if it is possible to trigger some of these with a "normal"
work-load on a "normal" kernel? Has anyone (perhaps ARM employees) looked
at that? (I suppose they have.)

For example, errata #782772
"Speculative execution of a Load-Exclusive or Store-Exclusive instruction
after a write to Strongly Ordered memory might deadlock the processor."
(The recommended work-around is a strategically-placed DMB.)

Since ldrex is used in low-level code, it seems possible to hit that one?
Or perhaps Linux does not support "Strongly Ordered" memory regions?

Regards.

next             reply	other threads:[~2015-03-20 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 16:30 Mason [this message]
2015-03-20 17:20 ` ERRATA work-arounds in the kernel Catalin Marinas
2015-03-20 21:40   ` Mason
2015-03-23 12:49     ` Catalin Marinas

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=550C4B12.1030608@free.fr \
    --to=slash.tmp@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox