From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Barry Song <21cnbao@gmail.com>
Cc: linux-omap@vger.kernel.org, yongsheng.liu@csr.com,
linaro-dev <linaro-dev@lists.linaro.org>,
peiyu.li@csr.com, DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Is Pandaboard cpuhotplug working stably?
Date: Wed, 21 Dec 2011 10:07:06 +0000 [thread overview]
Message-ID: <20111221100706.GC3354@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAGsJ_4w0iVXC6qmDzmkuOb=ZN=Q0bF7EAFkxeYR_d7-vo+8bqQ@mail.gmail.com>
On Wed, Dec 21, 2011 at 05:59:07PM +0800, Barry Song wrote:
> 2011/12/21 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> > cpu hotplug is basically totally buggered - the preconditions placed
> > upon the bringup code path are basically impossible to satisfy in any
> > shape or form at the moment.
> >
> > There's the requirement that the secondary CPU is marked online and
> > active before interrupts are enabled for the thread migration stuff
> > to behave correctly. However, this is incompatible with smp_call_function()
> > which will wait for online CPUs to respond to an IPI - which this one
> > won't because interrupts are disabled.
> >
> > I think there was some discussion about how to fix this but I don't
> > recall the details.
>
> thanks, Russell. then could i think this is an ARM-kernel-specific bug
> which exists on all ARM SMP chips for the moment?
> and that bug doesn't happen on x86:
I don't think so. There's nothing ARM specific about it.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-21 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 9:23 Is Pandaboard cpuhotplug working stably? Barry Song
2011-12-21 9:46 ` Russell King - ARM Linux
2011-12-21 9:59 ` Barry Song
2011-12-21 10:07 ` Russell King - ARM Linux [this message]
2011-12-22 8:49 ` Shilimkar, Santosh
2011-12-22 10:24 ` Russell King - ARM Linux
2011-12-22 10:27 ` Shilimkar, Santosh
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=20111221100706.GC3354@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=21cnbao@gmail.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=peiyu.li@csr.com \
--cc=workgroup.linux@csr.com \
--cc=yongsheng.liu@csr.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