From: William Lee Irwin III <wli@holomorphy.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Frank Cusack <fcusack@fcusack.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2nd proc not seen
Date: Mon, 29 Sep 2003 13:51:40 -0700 [thread overview]
Message-ID: <20030929205140.GQ4306@holomorphy.com> (raw)
In-Reply-To: <16247.63409.996071.860727@gargle.gargle.HOWL>
On Mon, Sep 29, 2003 at 11:13:21AM +0200, Mikael Pettersson wrote:
> Problem #1 is that physical CPU numbering isn't dense. This is not a bug.
> Problem #2 is that the kernel's internal dense-logical-to-sparse-physical
> numbering was deleted in 2.5.23 or thereabouts.
> Hence NR_CPUS is basically impossible to use reliably in 2.6 unless we
> reintroduce cpu_logical_map[].
We should be able to at least boot them, since we program logical ID's
ourselves. If you're relying on knowing physids at runtime you'll need
cpu_logical_map[].
-- wli
prev parent reply other threads:[~2003-09-29 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 9:11 2nd proc not seen Frank Cusack
2003-09-04 16:14 ` Frank Cusack
2003-09-29 3:50 ` Frank Cusack
2003-09-29 8:58 ` J.A. Magallon
2003-09-29 9:13 ` Mikael Pettersson
2003-09-29 20:51 ` William Lee Irwin III [this message]
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=20030929205140.GQ4306@holomorphy.com \
--to=wli@holomorphy.com \
--cc=fcusack@fcusack.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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).