From: William Lee Irwin III <wli@holomorphy.com>
To: Ethan Weinstein <lists@stinkfoot.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HT apparently not detected properly on 2.4.23
Date: Wed, 3 Dec 2003 16:46:11 -0800 [thread overview]
Message-ID: <20031204004611.GX8039@holomorphy.com> (raw)
In-Reply-To: <3FCE74B0.9010506@stinkfoot.org>
On Wed, Dec 03, 2003 at 06:41:36PM -0500, Ethan Weinstein wrote:
> Ok, setting CONFIG_NR_CPUS=8 does indeed solve the HT issue, looks like
> it was the numbering scheme:
Something like this might do the trick. NR_CPUS is already checked
indirectly via max_cpus.
-- wli
===== arch/i386/kernel/smpboot.c 1.17 vs edited =====
--- 1.17/arch/i386/kernel/smpboot.c Mon Nov 3 05:48:33 2003
+++ edited/arch/i386/kernel/smpboot.c Wed Dec 3 16:45:27 2003
@@ -1106,7 +1106,7 @@
*/
Dprintk("CPU present map: %lx\n", phys_cpu_present_map);
- for (bit = 0; bit < NR_CPUS; bit++) {
+ for (bit = 0; bit < BITS_PER_LONG; bit++) {
apicid = cpu_present_to_apicid(bit);
/* don't try to boot BAD_APICID */
prev parent reply other threads:[~2003-12-04 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 18:46 HT apparently not detected properly on 2.4.23 Ethan Weinstein
2003-12-03 19:40 ` Andre Tomt
2003-12-03 19:56 ` Mike Fedyk
2003-12-03 20:30 ` Ethan Weinstein
2003-12-03 22:40 ` William Lee Irwin III
2003-12-03 23:41 ` Ethan Weinstein
2003-12-03 23:58 ` William Lee Irwin III
2003-12-04 0:18 ` Ethan Weinstein
2003-12-05 17:12 ` Marcelo Tosatti
2003-12-05 17:48 ` William Lee Irwin III
2003-12-05 18:07 ` Re[2]: " Russell "Elik" Rademacher
[not found] ` <3FD0CD65.5080307@stinkfoot.org>
2003-12-05 23:02 ` Russell "Elik" Rademacher
2003-12-05 23:28 ` Ethan Weinstein
2003-12-05 23:31 ` Re[2]: " Russell "Elik" Rademacher
2003-12-05 23:38 ` William Lee Irwin III
2003-12-04 0:46 ` 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=20031204004611.GX8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@stinkfoot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.