LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: ak@suse.de, discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: x86_64: up to 255 or 256 CPUs?
Date: Mon, 19 Feb 2007 16:42:18 -0800 [thread overview]
Message-ID: <20070220004218.GO21484@holomorphy.com> (raw)
In-Reply-To: <20070220000647.GI13958@stusta.de>
On Tue, Feb 20, 2007 at 01:06:47AM +0100, Adrian Bunk wrote:
> Quoting arch/x86_64/Kconfig:
> <-- snip -->
> ...
> config NR_CPUS
> int "Maximum number of CPUs (2-256)"
> range 2 255
> ...
> <-- snip -->
> cu
> Adrian
The broadcast APIC ID clashes with the 256th cpu.
-- wli
next prev parent reply other threads:[~2007-02-20 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 0:06 x86_64: up to 255 or 256 CPUs? Adrian Bunk
2007-02-20 0:42 ` William Lee Irwin III [this message]
2007-02-20 9:35 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2007-01-11 7:01 Adrian Bunk
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=20070220004218.GO21484@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.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).