linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: MPCore v6_early_abort enhancement
Date: Sun, 13 Feb 2011 10:43:47 +0000	[thread overview]
Message-ID: <20110213104347.GA6138@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110211225342.GD236@mvista.com>

On Fri, Feb 11, 2011 at 05:53:42PM -0500, George G. Davis wrote:
> Hi,
> 
> On Fri, Feb 11, 2011 at 10:38:44PM +0000, Russell King - ARM Linux wrote:
> > On Sat, Feb 12, 2011 at 12:54:21AM +0300, Valentine Barshak wrote:
> > > SWP instruction sets bit 11 in DFSR, in case of data fault on SMP MPCore.
> > > So v6_early_abort doesn't need erratum 326103 workaround for MPCore.
> > 
> > NAK.  When building a SMP kernel which also supports v6 CPUs, this will
> > cause v6 CPUs to break.
> 
> Since the SWP erratum only affects ARM1136 (UP) processors, how will this
> break ARM11 MPCore (v6) processors?

Omitting the code will break MPcore processors.

> Are you referring to unified kernels which support both UP and SMP machines?

Of course.

> I reckon that's a recent feature to be able to boot SMP kernels on UP
> machines.

Makes no difference if it's a recent feature or not.  We're not adding
new obstacles to this when we're getting rid of them.  It's counter
productive.

> Perhaps if that's why you're against this, then we need to have a
> separate config option to specifically enable this ARM1136 erratum
> workaround?

No we don't.  Omitting the code is an optimization to what is already a
slow path which results in breakage for people.  That's why I nak'd it.

      reply	other threads:[~2011-02-13 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 21:54 [PATCH RFC] ARM: MPCore v6_early_abort enhancement Valentine Barshak
2011-02-11 22:38 ` Russell King - ARM Linux
2011-02-11 22:53   ` George G. Davis
2011-02-13 10:43     ` Russell King - ARM Linux [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=20110213104347.GA6138@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).