All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, Chuck Ebbert <cebbert@redhat.com>,
	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: Mon, 06 Oct 2008 00:45:36 +0200	[thread overview]
Message-ID: <48E94390.2080209@firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0810052252520.3398@apollo>


> Your proposed solution is:
> 
>      exporting additional_cpus  and change the check to:
> 
>      if ((num_possible_cpus() - additional_cpus) == 1 ...
> 
> This is simply stupid. We have the information already in
> num_present_cpus() and that's the correct check in the alternatives
> code.

Yes that is correct.  Using present_cpus is cleaner than
my version patch  (although it wasn't quite at a "mess" level imho).
No argument on that. But that  is not what my emails were about.

They were about the removal of the additional_cpus=... parameter
which was unfortunately done too.

additional_cpus is used for more than just alternatives processing.
It is also used to size the possible map and declare additional
hotplug CPUs.

Please read the Documentation cpu-hotplug-spec I referred to earlier
for background. Or Documentation/cpu-hotplug.txt which has it too.

additional_cpus is used to tell Linux that there are more (or less)
CPUs hotpluggable than the BIOS declares at boot time. This is needed
because the way the BIOS is declaring it is a Linux extension, not standard.
But even if it was standard it would be good policy to be able
to override it because as we all know BIOS can be wrong, as in
declare far too many.

But now that option is gone so this needed override isn't there

> additional_cpus is useless ballast.

For the alternatives heuristics yes. For hotplug no.

Only when you assume that all hotpluggable BIOS implement
the "cpu-hotplug-spec" Linux extension and always declare
hotplug correctly. That's quite dubious.

> 	tglx - who refrains from adding a nasty insulting comment

Feel free to speak your mind if the facts are correct.

-Andi


  reply	other threads:[~2008-10-05 22:45 UTC|newest]

Thread overview: 24+ 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
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 [this message]
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=48E94390.2080209@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.