public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"ananth@in.ibm.com" <ananth@in.ibm.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2 5/5] x86: use dmi check to treat disabled cpus as hotplug cpus.
Date: Tue, 12 Jan 2010 18:13:24 -0800	[thread overview]
Message-ID: <4B4D2C44.2060709@kernel.org> (raw)
In-Reply-To: <1263348363.2854.1360.camel@sbs-t61.sc.intel.com>

On 01/12/2010 06:06 PM, Suresh Siddha wrote:
> On Tue, 2010-01-12 at 17:55 -0800, Yinghai Lu wrote:
>> you mean this blacklist could be too long?
> 
> yes.
> 
>>
>> switch to whitelist for the box can treat disabled cpus as hotplug
>> cpus?
> 
> Do we really need all this? Systems which support physical hotplug
> typically have lot's of cpu's (mostly will have atleast > 8). Even if we
> really need to identify, then perhaps we can check if ACPI has any hints
> regarding the physical hotplug support at boot time (we should check
> with Andi Kleen or Len Brown on this).
> 
> For now, I think we can keep it simple by using the detected enabled
> cpu's.

sth like this ?

---
 arch/x86/kernel/smpboot.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

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
@@ -1190,7 +1190,6 @@ early_param("possible_cpus", _setup_poss
  * - Ashok Raj
  *
  * Three ways to find out the number of additional hotplug CPUs:
- * - If the BIOS specified disabled CPUs in ACPI/mptables use that.
  * - The user can overwrite it with possible_cpus=NUM
  * - Otherwise don't reserve additional CPUs.
  * We do this because additional CPUs waste a lot of memory.
@@ -1205,7 +1204,7 @@ __init void prefill_possible_map(void)
 		num_processors = 1;
 
 	if (setup_possible_cpus == -1)
-		possible = num_processors + disabled_cpus;
+		possible = num_processors;
 	else
 		possible = setup_possible_cpus;
 

  reply	other threads:[~2010-01-13  2:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 23:17 [PATCH 0/5] clean up logical flat apic mode using Yinghai Lu
2010-01-12 23:17 ` [PATCH -v2 1/5] use nr_cpus= to set nr_cpu_ids early Yinghai Lu
2010-01-12 23:17 ` [PATCH 2/5] x86: using logical flat for amd cpu too Yinghai Lu
2010-01-12 23:17 ` [PATCH -v2 3/5] x86: according to nr_cpu_ids to decide if need to leave logical flat Yinghai Lu
2010-01-12 23:17 ` [PATCH -v2 5/5] x86: use dmi check to treat disabled cpus as hotplug cpus Yinghai Lu
2010-01-12 23:56   ` Suresh Siddha
2010-01-13  0:05     ` Yinghai Lu
2010-01-13  1:48       ` Suresh Siddha
2010-01-13  1:55         ` Yinghai Lu
2010-01-13  2:06           ` Suresh Siddha
2010-01-13  2:13             ` Yinghai Lu [this message]
2010-01-13  2:21               ` Suresh Siddha
2010-01-13  2:26                 ` Yinghai Lu
2010-01-13 21:46       ` Andi Kleen
2010-01-13 22:00         ` H. Peter Anvin
2010-01-13 22:23           ` Andi Kleen
2010-01-13 22:27             ` H. Peter Anvin
2010-01-13 22:29               ` Suresh Siddha
2010-01-13 22:36                 ` H. Peter Anvin
2010-01-13 22:49                   ` Suresh Siddha
2010-01-13 23:02                     ` Yinghai Lu
2010-01-13 23:13                       ` H. Peter Anvin
2010-01-13 23:52                         ` Andi Kleen
2010-01-14  9:25                     ` Andi Kleen
2010-01-12 23:17 ` [PATCH 4/5] x86: make 32bit apic flat to physflat switch like 64bit Yinghai Lu

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=4B4D2C44.2060709@kernel.org \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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