All of lore.kernel.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: Handling ARM_ERRATA_364296 when CONFIG_SMP=y
Date: Fri, 12 Jul 2013 16:14:35 +0100	[thread overview]
Message-ID: <20130712151434.GF28271@arm.com> (raw)
In-Reply-To: <CAOMZO5AVpQ6DUja=usBCDzRH0NyNqbXsHNNOJSAY=8OvgHHTmA@mail.gmail.com>

On Mon, Jul 08, 2013 at 07:16:34PM +0100, Fabio Estevam wrote:
> On commit 145e10e1 (ARM: 7015/1: ARM errata: Possible cache data
> corruption with hit-under-miss enabled) you added support for
> ARM_ERRATA_364296 option:
> 
> +config ARM_ERRATA_364296
> +       bool "ARM errata: Possible cache data corruption with
> hit-under-miss enabled"
> +       depends on CPU_V6 && !SMP
> +       help
> 
> As this erratum affects mx31/mx35, I would like to enable it, but I am
> not allowed to do it because mx31/mx35 share the same config file as
> mx6 (imx_v6_v7_defconfig), which has SMP turned on.
> 
> What would be the correct approach for applying this erratum?
> 
> Is it safe to do "depends on CPU_V6" only or should this erratum be
> handled in the bootloader?

I think you can just remove the !SMP case. The workaround (setting an
undocumented bit) already checks for the right CPU Id. The only problem
issue is that oldconfig will ask whether to enable it or not.

Bootloader would be even better but it's pretty late to enforce this on
ARMv6.

-- 
Catalin

  parent reply	other threads:[~2013-07-12 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 18:16 Handling ARM_ERRATA_364296 when CONFIG_SMP=y Fabio Estevam
2013-07-08 18:22 ` Willy Tarreau
2013-07-08 20:29   ` Fabio Estevam
2013-07-08 21:10     ` Willy Tarreau
2013-07-12 15:14 ` Catalin Marinas [this message]
2013-07-12 15:19   ` Russell King - ARM Linux

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=20130712151434.GF28271@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 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.