From: Ingo Molnar <mingo@elte.hu>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: <PING> Re: [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time
Date: Sun, 5 Oct 2008 12:28:35 +0200 [thread overview]
Message-ID: <20081005102835.GA8947@elte.hu> (raw)
In-Reply-To: <20081004183014.769836ff@redhat.com>
* Chuck Ebbert <cebbert@redhat.com> wrote:
> Yes, it works and I don't see how it could cause any problems.
>
> Ingo, can we get this in 2.6.27? You can drop my original patch.
>
> Tested-by: Chuck Ebbert <cebbert@redhat.com>
looks good, applied to tip/x86/core, thanks!
it's too late for v2.6.27 (and not a serious regression anyway), but i
marked it for .27.1 backporting.
Your other patch still makes sense - as additional_cpus is an existing
boot parameter it can be specified at .config time as well. You should
not enable it in a distro kernel though, if you intend to support real
hotplug CPU hardware. (which is extremely rare btw.)
Ingo
next prev parent reply other threads:[~2008-10-05 10:28 UTC|newest]
Thread overview: 24+ 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
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 [this message]
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
[not found] <bijiX-86S-5@gated-at.bofh.it>
[not found] ` <bisvP-3es-3@gated-at.bofh.it>
[not found] ` <biC2k-7cR-17@gated-at.bofh.it>
[not found] ` <biCbU-7lA-15@gated-at.bofh.it>
[not found] ` <biCOy-8ep-3@gated-at.bofh.it>
[not found] ` <biD7T-5N-1@gated-at.bofh.it>
[not found] ` <bjiEh-2MC-21@gated-at.bofh.it>
[not found] ` <bjnXc-1ec-11@gated-at.bofh.it>
[not found] ` <bjz2s-78A-13@gated-at.bofh.it>
[not found] ` <bjDfK-40E-19@gated-at.bofh.it>
[not found] ` <bjDIN-4L8-31@gated-at.bofh.it>
[not found] ` <bjEbU-5eX-19@gated-at.bofh.it>
[not found] ` <bjIIi-2Oi-1@gated-at.bofh.it>
[not found] ` <bjJOk-49Q-5@gated-at.bofh.it>
[not found] ` <bjKAv-5bK-17@gated-at.bofh.it>
2008-10-06 10:59 ` Bodo Eggert
2008-10-06 13:22 ` 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=20081005102835.GA8947@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome