From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: vexpress: add support for CPU hotplug to ct-ca9x4 tile
Date: Wed, 8 Sep 2010 17:51:52 +0100 [thread overview]
Message-ID: <20100908165152.GA4177@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <000301cb4f75$52e66570$f8b33050$@deacon@arm.com>
On Wed, Sep 08, 2010 at 05:46:02PM +0100, Will Deacon wrote:
> Hi Russell,
>
> > On Tue, Aug 17, 2010 at 04:58:04PM +0100, Will Deacon wrote:
> > > The Versatile Express platform can support a quad-core Cortex-A9 tile running
> > > SMP Linux.
> > >
> > > This patch adds support for CPU hotplug when running in this configuration.
> >
> > This ties the core tile support into the generic versatile express code,
> > something which the current code structure is careful to avoid. Please
> > ensure that we continue to avoid making the generic code rely upon
> > CA9x4 code.
>
> The cpu_{enter,leave}_lowpower functions are implemented in the tile code
> so they should be ok. I suppose the problem is that we might be able to do
> better than a WFI on some tiles. How about this?:
What I was referring to is that generic code _directly_ calls tile code.
That means if you want to build in support for two tiles, you're going
to have symbols clashing as two tiles will define functions called
'cpu_enter_lowpower' etc.
prev parent reply other threads:[~2010-09-08 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 15:58 [PATCH 0/3] CPU hotplug support for Versatile platforms Will Deacon
2010-08-17 15:58 ` [PATCH 1/3] ARM: realview: fix CPU hotplug support for SMP platforms Will Deacon
2010-08-17 15:58 ` [PATCH 2/3] ARM: plat-versatile: factor out common hotplug code Will Deacon
2010-08-17 15:58 ` [PATCH 3/3] ARM: vexpress: add support for CPU hotplug to ct-ca9x4 tile Will Deacon
2010-09-08 14:37 ` Russell King - ARM Linux
2010-09-08 16:46 ` Will Deacon
2010-09-08 16:51 ` 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=20100908165152.GA4177@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.