From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: frankeh@watson.ibm.com, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: SMP BUG
Date: Wed, 15 Feb 2006 23:34:10 +0000 [thread overview]
Message-ID: <20060215233410.GE1508@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060215151716.201da5de.akpm@osdl.org>
On Wed, Feb 15, 2006 at 03:17:16PM -0800, Andrew Morton wrote:
> Is arm's setup_arch() populating cpu_possible_map?
Correct, because setup_arch() itself doesn't have _any_ SMP awareness at
all - only the platform code knows about that. Hence, we initialise it
in smp_prepare_cpus(), which is a platform specific function.
> If that's not possible, statically initialising it to CPU_MASK_ALL should
> fix it, but that's a lame solution and might lead to wastage of per-cpu
> memory on not-possible CPUs.
I think that's what we'll have to do, and then later on clear it and
re-populate it with the correct bitmask. Grumble.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-02-15 23:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 0:19 SMP BUG Hubertus Franke
2006-02-15 23:07 ` Russell King
2006-02-15 23:17 ` Andrew Morton
2006-02-15 23:34 ` Russell King [this message]
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
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=20060215233410.GE1508@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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