From: Chuck Ebbert <cebbert@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time
Date: Thu, 2 Oct 2008 15:25:21 -0400 [thread overview]
Message-ID: <20081002152521.16c4835b@redhat.com> (raw)
In-Reply-To: <87bpy3pdgs.fsf@basil.nowhere.org>
On Thu, 02 Oct 2008 11:12:51 +0200
Andi Kleen <andi@firstfloor.org> wrote:
> Chuck Ebbert <cebbert@redhat.com> writes:
>
> > 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.
>
> You can set this with additional_cpus=... at boot time.
> I don't think each runtime option needs a CONFIG option too.
>
Well not all of them, but this one is a good candidate. Either that or
we should just change the default to zero.
next prev parent reply other threads:[~2008-10-02 19:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 23:19 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
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 [this message]
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=20081002152521.16c4835b@redhat.com \
--to=cebbert@redhat.com \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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