From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] CPU hotplug support for Versatile platforms
Date: Sat, 18 Sep 2010 00:01:27 +0100 [thread overview]
Message-ID: <20100917230127.GA19718@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4C93DBE6.2040103@gmail.com>
On Fri, Sep 17, 2010 at 04:21:42PM -0500, Rob Herring wrote:
> The platform specific SMP code is one area that prevents supporting a
> single kernel image. All the functions in platsmp.c need to be converted
> to function pointers and a lot of that code is pretty simliar across
> platforms. What's needed is a common platsmp.c with something like
> platform specific smp_ops like PowerPC. I think addressing that first
> would simplify this restructuring as you are doing some of what's
> needed, but you introducing new namespace problems like platform_cpu_*.
The split between smp.c and platsmp.c is there to allow different SMP
implementations from the standard ARM Ltd SMP implementation (and there
will be different implementations.)
Just because all the SMP implementations that are currently merged are
the standard ARM Ltd SMP implementation does not mean that we should
move stuff out of platsmp.c into the generic code.
next prev parent reply other threads:[~2010-09-17 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 13:12 [PATCH 0/4] CPU hotplug support for Versatile platforms Will Deacon
2010-09-17 13:12 ` [PATCH 1/4] ARM: vexpress: add support for multiple core tiles Will Deacon
2010-09-17 13:12 ` [PATCH 2/4] ARM: realview: fix CPU hotplug support for SMP platforms Will Deacon
2010-09-17 13:12 ` [PATCH 3/4] ARM: plat-versatile: factor out common hotplug code Will Deacon
2010-09-17 13:12 ` [PATCH 4/4] ARM: vexpress: add support for CPU hotplug to ct-ca9x4 tile Will Deacon
2010-09-17 21:21 ` [PATCH 0/4] CPU hotplug support for Versatile platforms Rob Herring
2010-09-17 23:01 ` Russell King - ARM Linux [this message]
2010-09-18 20:58 ` Rob Herring
2010-09-22 17:45 ` Will Deacon
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=20100917230127.GA19718@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).