From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Fabio Estevam <festevam@gmail.com>,
linux-omap@vger.kernel.org,
afzal mohammed <afzal.mohd.ma@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@kernel.org>
Subject: Re: [CFT] Always enable SMP mode on MP capable CPUs
Date: Wed, 31 May 2017 07:39:15 -0700 [thread overview]
Message-ID: <20170531143914.GD3730@atomide.com> (raw)
In-Reply-To: <20170527132237.GX23750@n2100.armlinux.org.uk>
* Russell King - ARM Linux <linux@armlinux.org.uk> [170527 06:26]:
> On Fri, May 26, 2017 at 04:52:10PM +0530, afzal mohammed wrote:
> > Hi,
> >
> > On Thu, May 25, 2017 at 03:13:33PM -0700, Tony Lindgren wrote:
> >
> > > OK so got my am437x-idk back
> > >
> > > And as suspected it won't boot with these changes.
> >
> > Tested here too with your additional changes included & seeing same
> > behavior here as well on AM437x.
> >
> > As an aside, when Russell posted this patch a week back itself was
> > suspecting this. i had a certain view on AM437x w.r.t SMP issue back
> > while officially working on it & since now not officially involved
> > with the issue at hand, i was uncomfortable dealing with this. But as
> > Russell's patch was not noticed by others w.r.t AM437x, upon being
> > able to confirm it yesterday, i at least wanted to bring it to notice
> > & runaway from the scene.
>
> Right, so I think the summary is: the kernel can't set the SMP bit
> correctly - it doesn't have the information at this point in time
> to know definitively whether the bit needs to be set or not.
>
> So, those who are suffering issues with their SMP cores in uniprocessor
> systems need to ensure that their boot loader correctly configures the
> CPU cores.
Russell, current Linux next still has commit e7cf836e9757 ("ARM:
always enable SMP mode on SMP cores"). You're planning to drop
it, right?
It causes a regression on am437x to not boot as we can't set the
SMP bit on it.
Regards,
Tony
next prev parent reply other threads:[~2017-05-31 14:39 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 [this message]
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
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=20170531143914.GD3730@atomide.com \
--to=tony@atomide.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=festevam@gmail.com \
--cc=khilman@kernel.org \
--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).