linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: Russell King <linux@arm.linux.org.uk>,
	Shawn Guo <shawn.guo@linaro.org>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Nicolas Pitre <nico@linaro.org>,
	Marc Carino <marc.ceeeee@gmail.com>,
	Mahesh Sivasubramanian <msivasub@codeaurora.org>,
	Jonathan Austin <Jonathan.Austin@arm.com>,
	"heiko@sntech.de" <heiko@sntech.de>,
	"addy.ke@rock-chips.com" <addy.ke@rock-chips.com>,
	"xjq@rock-chips.com" <xjq@rock-chips.com>,
	"cf@rock-chips.com" <cf@rock-chips.com>,
	"hj@rock-chips.com" <hj@rock-chips.com>,
	"huangtao@rock-chips.com" <huangtao@rock-chips.com>,
	Ben Dooks <ben.dooks@codethink.co.uk>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: errata: Workaround for Cortex-A12 erratum 818325
Date: Tue, 26 Aug 2014 11:14:14 +0100	[thread overview]
Message-ID: <20140826101414.GD23445@arm.com> (raw)
In-Reply-To: <1408355889-4176-1-git-send-email-kever.yang@rock-chips.com>

On Mon, Aug 18, 2014 at 10:58:09AM +0100, Kever Yang wrote:
> From: Huang Tao <huangtao@rock-chips.com>
> 
> On Cortex-A12 (r0p0..r0p1-00lac0-rc11), when a CPU executes a sequence of
> two conditional store instructions with opposite condition code and
> updating the same register, the system might enter a deadlock if the
> second conditional instruction is an UNPREDICTABLE STR or STM
> instruction. This workaround setting bit[12] of the Feature Register
> prevents the erratum. This bit disables an optimisation applied to a
> sequence of 2 instructions that use opposing condition codes.
> 
> Signed-off-by: Huang Tao <huangtao@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---

The Rk3288 I have advertises itself as an r0p1 Cortex-A12 CPU, so isn't
affected by this issue. Until we have an SoC supported in mainline that
requires this workaround, I don't think we should merge it.

Also, please consider setting these bits in your firmware if possible.
The feature register isn't writable from the non-secure side, so if you
want to use virtualisation you'll need to do this differently.

Will

  parent reply	other threads:[~2014-08-26 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18  9:58 [PATCH] ARM: errata: Workaround for Cortex-A12 erratum 818325 Kever Yang
2014-08-26  8:49 ` Kever Yang
2014-08-26 10:14 ` Will Deacon [this message]
2014-08-26 11:36   ` 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=20140826101414.GD23445@arm.com \
    --to=will.deacon@arm.com \
    --cc=Jonathan.Austin@arm.com \
    --cc=addy.ke@rock-chips.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=cf@rock-chips.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=heiko@sntech.de \
    --cc=hj@rock-chips.com \
    --cc=huangtao@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marc.ceeeee@gmail.com \
    --cc=msivasub@codeaurora.org \
    --cc=nico@linaro.org \
    --cc=shawn.guo@linaro.org \
    --cc=xjq@rock-chips.com \
    /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).