linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cbouatmailru@gmail.com (Anton Vorontsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: SCU: Add generic routines for secondary CPU bootup
Date: Sat, 31 Jul 2010 20:38:54 +0400	[thread overview]
Message-ID: <20100731163854.GA19180@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20100731154134.GF27064@n2100.arm.linux.org.uk>

On Sat, Jul 31, 2010 at 04:41:34PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jul 27, 2010 at 09:11:40PM +0400, Anton Vorontsov wrote:
> > For CNS3xxx we want to reuse the original ARM approach of booting
> > secondary CPUs. This patch turns VExpress' code into "SCU library",
> > so that now platform code can call the generic routines.
> 
> I'm not sure this should become a "SCU library" - the name seems wrong.

Well, how would you name it? Would you also move these routines
into a separate file (is there any preference for the file name)?

> When you consider that the SCU is the 'snoop control unit', which has
> no relation to how secondary CPUs are booted, it makes little sense.
> 
> The secondary CPU boot protocol has much more to do with the boot
> loader than with the hardware.

Yup.

> I also suspect that we can get rid of the 'holding pen' stuff and just
> rely on the IPI being sent to the intended target CPU.  I don't think
> anyone has really updated this since the initial ARM SMP implementation.

Sure, but I belive that this patch set is a step into the right
direction, basically it just gets rid of code duplication, and
then we can improve the bootup code for all interested machines.

With these patches, machines don't* bother with the holding pen,
it just becomes an implementation detail of the SCU/secondary
CPU bootup code.

So it makes sense to consolidate the code anyway (which exactly
what these patches do), right?

* Except realview, it also uses scu_pen_release for hotplug
  handling.

-- 
Anton Vorontsov
email: cbouatmailru at gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2010-07-31 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 17:11 [PATCH v3 0/4] SMP support for CNS3xxx + some SMP SCU cleanups Anton Vorontsov
2010-07-27 17:11 ` [PATCH 1/4] ARM: SCU: Add generic routines for secondary CPU bootup Anton Vorontsov
2010-07-31 15:41   ` Russell King - ARM Linux
2010-07-31 16:38     ` Anton Vorontsov [this message]
2010-07-27 17:11 ` [PATCH 2/4] ARM: cns3xxx: Add support for SMP Anton Vorontsov
2010-07-27 17:11 ` [PATCH 3/4] ARM: VExpress: Switch to generic SCU routines Anton Vorontsov
2010-07-27 17:11 ` [PATCH 4/4] ARM: RealView: " 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=20100731163854.GA19180@oksana.dev.rtsoft.ru \
    --to=cbouatmailru@gmail.com \
    --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).