From: James Bottomley <James.Bottomley@SteelEye.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
stsp@aknet.ru, linux-kernel@vger.kernel.org
Subject: Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data
Date: Tue, 27 Jun 2006 09:01:15 -0500 [thread overview]
Message-ID: <1151416875.3340.6.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <31382.1151413209@ocs3.ocs.com.au>
On Tue, 2006-06-27 at 23:00 +1000, Keith Owens wrote:
> AFAICR, the BSP is supposed to be logical cpu 0 on all architectures.
> Most architectures assign logical cpu 0 to the BSP, even if the BSP
> has
> a non-zero hard_smp_processor_id. ia64 even has this
That's definitely not a requirement. For systems like voyager whose
CPUs cannot be renumbered it makes no sense. The original reason for
renumbering was that most CPU loops ran from 1 to max_cpu and therefore
worked better if the CPU map was dense. However, I fixed that up long
ago so sparse CPU map traversal should be fine now.
James
next prev parent reply other threads:[~2006-06-27 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 2:45 James Bottomley
2006-06-27 3:04 ` Andrew Morton
2006-06-27 3:36 ` James Bottomley
2006-06-27 5:03 ` Andrew Morton
2006-06-27 13:00 ` Keith Owens
2006-06-27 14:01 ` James Bottomley [this message]
2006-06-27 14:49 ` James Bottomley
2006-06-28 0:04 ` Andrew Morton
2006-06-28 2:45 ` James Bottomley
2006-06-28 2:57 ` Andrew Morton
2006-06-28 23:10 ` James Bottomley
2006-06-29 16:58 ` James Bottomley
2006-07-02 14:52 ` Eric W. Biederman
2006-07-02 15:06 ` James Bottomley
2006-07-02 15:37 ` Eric W. Biederman
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=1151416875.3340.6.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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
all inboxes | Powered by JetHome®