From: Rob Radez <rob@osinvestor.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_NR_CPUS, redux
Date: Tue, 11 Jun 2002 16:10:59 -0400 [thread overview]
Message-ID: <20020611161059.N30977@osinvestor.com> (raw)
In-Reply-To: <1023817936.21176.232.camel@sinai>
On Tue, Jun 11, 2002 at 10:52:16AM -0700, Robert Love wrote:
> Andrew has pointed out some architectures may need minor tweaks to work
> with NR_CPUS < 32. He discovered and fixed a minor issue on i386...
> other architectures, please verify non-standard options work. Also make
On sparc, setting NR_CPUS to anything other than 32 with CONFIG_SMP set
breaks. Simple, stupid patch is attached, but there's a more elegant fix to
the actual functions abusing NR_CPUS that just seems much nicer ;-).
And yes, I know, sparc on 2.5 is badly broken, but this just might help keep
the broken-ness down a little bit.
Regards,
Rob Radez
diff -Nru a/include/asm-sparc/smp.h b/include/asm-sparc/smp.h
--- a/include/asm-sparc/smp.h Tue Jun 11 16:09:48 2002
+++ b/include/asm-sparc/smp.h Tue Jun 11 16:09:48 2002
@@ -31,7 +31,7 @@
#include <asm/ptrace.h>
#include <asm/asi.h>
-extern struct prom_cpuinfo linux_cpus[NR_CPUS];
+extern struct prom_cpuinfo linux_cpus[32];
/* Per processor Sparc parameters we need. */
next prev parent reply other threads:[~2002-06-11 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 17:52 Robert Love
2002-06-11 18:09 ` Randy.Dunlap
2002-06-11 18:19 ` Robert Love
2002-06-11 18:21 ` Ruth Ivimey-Cook
2002-06-11 18:28 ` Robert Love
2002-06-12 1:36 ` jw schultz
2002-06-12 15:06 ` Martin J. Bligh
2002-06-12 15:22 ` William Lee Irwin III
2002-06-11 18:29 ` Martin Dalecki
2002-06-11 23:20 ` Dave Jones
2002-06-13 8:51 ` Helge Hafting
2002-06-19 11:53 ` Bill Davidsen
2002-06-11 20:10 ` Rob Radez [this message]
2002-06-12 3:29 Matt_Domsch
2002-06-12 4:13 ` Austin Gonyou
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=20020611161059.N30977@osinvestor.com \
--to=rob@osinvestor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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®