linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: linux-omap@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	afzal mohammed <afzal.mohd.ma@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [CFT] Always enable SMP mode on MP capable CPUs
Date: Thu, 25 May 2017 10:10:00 -0700	[thread overview]
Message-ID: <20170525171000.GD10472@atomide.com> (raw)
In-Reply-To: <20170525165651.GK22219@n2100.armlinux.org.uk>

* Russell King - ARM Linux <linux@armlinux.org.uk> [170525 10:00]:
> On Thu, May 25, 2017 at 09:15:19AM -0700, Florian Fainelli wrote:
> > On 05/18/2017 03:52 AM, Russell King - ARM Linux wrote:
> > > As a result of a recent bug report, it has been found that certain CPUs
> > > must always have SMP mode enabled in order for the caches to work.
> > > 
> > > Remove the conditional on setting the SMP bit(s).
> > > 
> > > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> > > ---
> > > This needs to be tested on:
> > > 
> > > - Cortex A5MP
> > > - Cortex A9MP
> > > - Cortex R7MP
> > > - Cortex A7MP
> > > - Cortex A12MP
> > > - Cortex A15MP
> > > - Cortex A17MP
> > > - Brahma B15
> > 
> > Sorry just saw this, what kind of test do you want me to run on B15?
> > Should I build a !SMP kernel, or force a SMP kernel with maxcpus=1?
> 
> What I'm after is testing on any single-core systems with these SMP
> capable cores.  If the core never appears in a single-core configuration,
> then please let me know so it can be crossed off the list.
> 
> With the bug that crept in fixed (as pointed out by Tony) there is no
> difference for kernels built with SMP enabled and detected as a SMP
> capable CPU.

At least am437x needs to be tested as it's UP with some quirks.

Regards,

Tony

      parent reply	other threads:[~2017-05-25 17:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170518105209.GN22219@n2100.armlinux.org.uk>
     [not found] ` <CAOMZO5Da2R2_t2nU+MdrJiSzvcBQKS4pwYS96r4UyfGc8DtWww@mail.gmail.com>
     [not found]   ` <CAOMZO5Dc=i7UdQH=r5RRr_4GmyZZT+rh7BTNV4WbfqKvtVDfsw@mail.gmail.com>
     [not found]     ` <20170519171526.GW22219@n2100.armlinux.org.uk>
2017-05-24 15:38       ` [CFT] Always enable SMP mode on MP capable CPUs Tony Lindgren
2017-05-25 14:48         ` Russell King - ARM Linux
2017-05-25 15:11           ` Tony Lindgren
2017-05-25 18:05             ` Russell King - ARM Linux
2017-05-25 22:13               ` Tony Lindgren
2017-05-26 11:22                 ` afzal mohammed
2017-05-27 13:22                   ` Russell King - ARM Linux
2017-05-31 14:39                     ` Tony Lindgren
2017-05-31 14:59                       ` Russell King - ARM Linux
2017-05-31 15:07                         ` Tony Lindgren
2017-05-24 15:50 ` afzal mohammed
     [not found] ` <828a8817-b18d-6945-f35e-115abf30fe17@gmail.com>
     [not found]   ` <20170525165651.GK22219@n2100.armlinux.org.uk>
2017-05-25 17:10     ` Tony Lindgren [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=20170525171000.GD10472@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal.mohd.ma@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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).