From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH] x86: allow 8 more cpus could be used
Date: Thu, 29 Jan 2009 14:18:05 -0800 [thread overview]
Message-ID: <49822B1D.9070708@kernel.org> (raw)
Impact: fix left out MARCO
X86_PC will be always enabled. so need to check if we have bigsmp support built
in before cut off more than 8 cpus.
otherwise only get 8 cpus.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
arch/x86/kernel/smpboot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/arch/x86/kernel/smpboot.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/smpboot.c
+++ linux-2.6/arch/x86/kernel/smpboot.c
@@ -1000,7 +1000,7 @@ static int __init smp_sanity_check(unsig
{
preempt_disable();
-#if defined(CONFIG_X86_PC) && defined(CONFIG_X86_32)
+#if defined(CONFIG_X86_PC) && !defined(CONFIG_X86_BIGSMP)
if (def_to_bigsmp && nr_cpu_ids > 8) {
unsigned int cpu;
unsigned nr;
next reply other threads:[~2009-01-29 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:18 Yinghai Lu [this message]
2009-01-29 22:19 ` [PATCH] x86: don't treat bigsmp as no standard Yinghai Lu
2009-01-30 14:25 ` Ingo Molnar
2009-01-29 22:42 ` [PATCH] x86: allow 8 more cpus could be used Ingo Molnar
2009-01-29 22:44 ` Yinghai Lu
2009-01-29 23:08 ` Ingo Molnar
2009-01-29 23:14 ` Yinghai Lu
2009-01-29 23:20 ` Ingo Molnar
2009-01-29 22:44 ` Randy Dunlap
2009-01-29 23:12 ` Ingo Molnar
2009-01-29 23:14 ` Randy Dunlap
2009-01-29 23:22 ` Ingo Molnar
2009-01-29 23:23 ` Yinghai Lu
2009-01-29 23:25 ` Randy Dunlap
2009-01-30 0:09 ` Ingo Molnar
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=49822B1D.9070708@kernel.org \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.