From: GoatZilla <goatzilla@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: compiling 2.6.31, SMP with NR_CPUS == 1
Date: Thu, 17 Sep 2009 12:28:02 -0500 [thread overview]
Message-ID: <39e348480909171028id91fb7fsa721cf45805587ac@mail.gmail.com> (raw)
In-Reply-To: <39e348480909171025v21290799jc974c650b6c04379@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 162 bytes --]
I'm not sure if this is just me, or it's already been fixed, but in
include/linux/cpumask.h, if nr_cpu_ids is defined to "1", doesn't that
break init/main.c:368?
[-- Attachment #2: cpumask.patch --]
[-- Type: application/octet-stream, Size: 623 bytes --]
--- cpumask.h 14 Sep 2009 23:14:14 -0000 1.1.1.1
+++ cpumask.h 17 Sep 2009 16:55:09 -0000
@@ -396,7 +396,9 @@
#if NR_CPUS == 1
-#define nr_cpu_ids 1
+/* See init/main.c:368 */
+extern int nr_cpu_ids;
+
#ifndef CONFIG_DISABLE_OBSOLETE_CPUMASK_FUNCTIONS
#define first_cpu(src) ({ (void)(src); 0; })
#define next_cpu(n, src) ({ (void)(src); 1; })
@@ -406,7 +408,6 @@
#endif /* !CONFIG_DISABLE_OBSOLETE_CPUMASK_FUNCTIONS */
#else /* NR_CPUS > 1 */
-extern int nr_cpu_ids;
#ifndef CONFIG_DISABLE_OBSOLETE_CPUMASK_FUNCTIONS
int __first_cpu(const cpumask_t *srcp);
int __next_cpu(int n, const cpumask_t *srcp);
parent reply other threads:[~2009-09-17 17:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <39e348480909171025v21290799jc974c650b6c04379@mail.gmail.com>]
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=39e348480909171028id91fb7fsa721cf45805587ac@mail.gmail.com \
--to=goatzilla@gmail.com \
--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
all inboxes | Powered by JetHome®