From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] ARM: SCU: Add common routines for secondary CPU bootup
Date: Thu, 2 Dec 2010 17:38:24 +0000 [thread overview]
Message-ID: <20101202173824.GE10461@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1291307320.11271.51.camel@e102109-lin.cambridge.arm.com>
On Thu, Dec 02, 2010 at 04:28:40PM +0000, Catalin Marinas wrote:
> The SCU is part of the core TRM, so I don't expect it to be the same
> across various MP cores (and A15 is an example).
>
> You may want to consolidate functions like scu_prepare_cpus (maybe call
> it smp_prepare_cpus)
You do realise the function called from architecture independent code is
called 'smp_prepare_cpus' ?
> and something that calls set_cpu_possible() but
> with platform callbacks for getting the number of calls and initialising
> the SMP (SCU for most platforms).
What if a platform, for what ever reason, wants to have 3 CPUs,
numbered 0, 2, 3 ? That's the reason why the code which sets the
possible and present maps isn't in the ARM core code - Eg, we don't
know if a platform wants to keep CPU 1 in AMP mode to run some
special software on it.
> Whether this is worth, I don't know.
I don't think it's worth it because I think trying to considate this
is going to cripple the code structure in the future.
What we currently have is a nice sane separation of the core SMP
support from the platform specific parts of the SMP support.
BTW, is it worth making sure that the IC and SCU standby mode bits
are set for A9 MPCore ?
next prev parent reply other threads:[~2010-12-02 17:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 17:16 [PATCH v4 0/8] SMP support for CNS3xxx + some SMP SCU cleanups Anton Vorontsov
2010-11-30 17:16 ` [PATCH 1/8] ARM: SCU: Add common routines for secondary CPU bootup Anton Vorontsov
2010-11-30 22:24 ` Russell King - ARM Linux
2010-11-30 23:32 ` Russell King - ARM Linux
2010-12-01 0:25 ` Russell King - ARM Linux
2010-12-02 15:19 ` Catalin Marinas
2010-12-02 15:24 ` Russell King - ARM Linux
2010-12-02 16:28 ` Catalin Marinas
2010-12-02 17:38 ` Russell King - ARM Linux [this message]
2010-12-02 17:55 ` Catalin Marinas
2010-12-02 18:01 ` Russell King - ARM Linux
2010-12-04 8:48 ` Russell King - ARM Linux
2010-12-06 7:28 ` [PATCH 1/8] ARM: SCU: Add common routines for secondary CPUbootup Santosh Shilimkar
2010-12-01 6:21 ` [PATCH 1/8] ARM: SCU: Add common routines for secondary CPU bootup Srinidhi Kasagar
2010-11-30 17:17 ` [PATCH 2/8] ARM: cns3xxx: Add support for SMP Anton Vorontsov
2010-11-30 18:14 ` Russell King - ARM Linux
2010-11-30 17:17 ` [PATCH 3/8] ARM: VExpress: Switch to generic SCU routines Anton Vorontsov
2010-11-30 23:27 ` Russell King - ARM Linux
2010-11-30 17:17 ` [PATCH 4/8] ARM: RealView: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 5/8] ARM: S5PV310: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 6/8] ARM: ux500: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 7/8] ARM: tegra: " Anton Vorontsov
2010-11-30 17:17 ` [PATCH 8/8] ARM: OMAP2: " Anton Vorontsov
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=20101202173824.GE10461@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).