From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: torvalds@osdl.org, frankeh@watson.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: SMP BUG
Date: Wed, 15 Feb 2006 16:28:36 -0800 [thread overview]
Message-ID: <20060215162836.278cfafb.akpm@osdl.org> (raw)
In-Reply-To: <20060216001409.GG1508@flint.arm.linux.org.uk>
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> > So I think it's sanest to say that the arch shalt initialise cpu_possible_map
> > in setup_arch().
>
> Is that the only thing which needs to be initialised early for SMP, or
> are there other changes with early SMP init looming?
Well, I'm not aware of anything - just the patch "percpu data changes" I
sent to linux-arch the other day, which is related to this issue.
The whole early bootup what-the-arch-should-do-when protocol is rather a
mess, so I'm sure other things will need changing.
> The reason I ask is that the cleanest solution for ARM would be to
> introduce yet another initialisation function for MP platforms to
> implement, which setup_arch() will call after the initial page tables
> have been setup. Hence, I'm wondering if the platform specific parts
> could be simplified by moving more stuff earlier.
That sounds sane. Perhaps make it a generic setup_arch_platform() whose
mandate is "do whatever needs to be done for setup_arch()".
next prev parent reply other threads:[~2006-02-16 0:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 0:19 Hubertus Franke
2006-02-15 23:07 ` Russell King
2006-02-15 23:17 ` Andrew Morton
2006-02-15 23:34 ` Russell King
2006-02-15 23:23 ` Linus Torvalds
2006-02-15 23:30 ` Andrew Morton
2006-02-15 23:37 ` Russell King
2006-02-15 23:46 ` Andrew Morton
2006-02-16 0:14 ` Russell King
2006-02-16 0:28 ` Andrew Morton [this message]
2006-02-16 0:52 ` Linus Torvalds
2006-02-16 3:29 ` Nick Piggin
2006-02-16 8:37 ` Ingo Molnar
2006-02-16 10:20 ` Russell King
2006-02-16 15:54 ` Linus Torvalds
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=20060215162836.278cfafb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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
Powered by JetHome