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 17:55:29 -0800 [thread overview]
Message-ID: <4B4D2811.7000001@kernel.org> (raw)
In-Reply-To: <1263347315.2854.1296.camel@sbs-t61.sc.intel.com>
On 01/12/2010 05:48 PM, Suresh Siddha wrote:
> On Tue, 2010-01-12 at 16:05 -0800, Yinghai Lu wrote:
>> On 01/12/2010 03:56 PM, Suresh Siddha wrote:
>>> On Tue, 2010-01-12 at 15:17 -0800, Yinghai Lu wrote:
>>>> some systems that have disable cpus entries because same
>>>> BIOS will support 2 sockets and 4 sockets and more at
>>>> same time, BIOS just leave some disable entries, but
>>>> those system do not support cpu hotplug. we don't need
>>>> treat disabled_cpus as hotplug cpus.
>>>> so we can make nr_cpu_ids smaller and save more space
>>>> (pcpu data allocations), and could make some systems run
>>>> with logical flat instead of physical flat apic mode
>>>>
>>>> -v2: change to black list instead
>>>
>>> I don't think this list will work because every HT system with HT
>>> disabled in the bios shows that logical cpu as disabled.
>>
>> so you want to treat those disabled cpus in the those system as hotplug cpus or not?
>
> They are really not hot plug cpus, so they can also take advantage of
> what you are trying to provide with this patch.
you mean this blacklist could be too long?
switch to whitelist for the box can treat disabled cpus as hotplug cpus?
>
> Also I am very confused with what exactly you are doing with the dmi
> list..
>
> + printk(KERN_NOTICE "%s detected: treat disabled cpus as hotplug ones\n", d->ident);
> + treat_disabled_cpus_as_hotplug = 0;
>
sorry, forget to change the print out.
YH
next prev parent reply other threads:[~2010-01-13 1:57 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 [this message]
2010-01-13 2:06 ` Suresh Siddha
2010-01-13 2:13 ` Yinghai Lu
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=4B4D2811.7000001@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