From: Ingo Molnar <mingo@elte.hu>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time, V2
Date: Thu, 2 Oct 2008 21:42:15 +0200 [thread overview]
Message-ID: <20081002194215.GA8078@elte.hu> (raw)
In-Reply-To: <20081002153007.2e031232@redhat.com>
* Chuck Ebbert <cebbert@redhat.com> wrote:
> From: Chuck Ebbert <cebbert@redhat.com>
>
> x86: allow number of additional hotplug CPUs to be set at compile time, V2
>
> The default number of additional CPU IDs for hotplugging is determined
> by asking ACPI or mptables how many "disabled" CPUs there are in the
> system, but many systems get this wrong so that e.g. a uniprocessor
> machine gets an extra CPU allocated and never switches to single CPU
> mode.
>
> And sometimes CPU hotplugging is enabled only for suspend/hibernate
> anyway, so the additional CPU IDs are not wanted. Allow the number to
> be set to zero at compile time.
>
> Also, force the number of extra CPUs to zero if hotplugging is disabled
> which allows removing some conditional code.
>
> Tested on uniprocessor x86_64 that ACPI claims has a disabled processor,
> with CPU hotplugging configured.
>
> ("After" has the number of additional CPUs set to 0)
> Before: NR_CPUS: 512, nr_cpu_ids: 2, nr_node_ids 1
> After: NR_CPUS: 512, nr_cpu_ids: 1, nr_node_ids 1
>
> [Changed the name of the option and the prompt according to Ingo's
> suggestion.]
> +config HOTPLUG_RESTRICT_TO_BOOTUP_CPUS
> + def_bool n
> + prompt "Restrict CPU hotplugging to processors found during boot" if HOTPLUG_CPU
ok, that description and naming makes the purpose much clearer, and it's
default-disabled as well.
Applied to tip/x86/core, thanks Chuck!
note that this chunk:
> @@ -1282,16 +1282,13 @@ __init void prefill_possible_map(void)
> if (!num_processors)
> num_processors = 1;
>
> -#ifdef CONFIG_HOTPLUG_CPU
> if (additional_cpus == -1) {
> if (disabled_cpus > 0)
> additional_cpus = disabled_cpus;
> else
> additional_cpus = 0;
> }
> -#else
> - additional_cpus = 0;
> -#endif
> +
was already in -tip, by virtue of:
| commit 2bd455dbfebfd632a8dcf1d3d1612737986fde0a
| Author: Li Zefan <lizf@cn.fujitsu.com>
| Date: Mon Aug 4 11:26:38 2008 +0800
|
| x86: remove nesting CONFIG_HOTPLUG_CPU
please double-check latest tip/master nevertheless:
http://people.redhat.com/mingo/tip.git/README
to make sure i merged your patch correctly and that it plays well with
other changes.
Thanks,
Ingo
next prev parent reply other threads:[~2008-10-02 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 23:19 [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time Chuck Ebbert
2008-10-02 8:12 ` Ingo Molnar
2008-10-02 19:30 ` [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time, V2 Chuck Ebbert
2008-10-02 19:42 ` Ingo Molnar [this message]
2008-10-02 19:48 ` H. Peter Anvin
2008-10-02 19:50 ` Ingo Molnar
2008-10-02 9:12 ` [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time Andi Kleen
2008-10-02 19:25 ` Chuck Ebbert
2008-10-02 19:44 ` Andi Kleen
2008-10-02 20:09 ` Chuck Ebbert
2008-10-02 20:40 ` Andi Kleen
2008-10-04 16:52 ` <PING> " Andi Kleen
2008-10-04 22:30 ` Chuck Ebbert
2008-10-05 10:28 ` Ingo Molnar
2008-10-05 14:52 ` Thomas Gleixner
2008-10-05 15:20 ` Ingo Molnar
2008-10-05 15:51 ` Thomas Gleixner
2008-10-05 15:56 ` Ingo Molnar
2008-10-05 20:39 ` Andi Kleen
2008-10-05 21:49 ` Thomas Gleixner
2008-10-05 22:45 ` Andi Kleen
2008-10-05 20:28 ` Andi Kleen
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=20081002194215.GA8078@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=cebbert@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome