All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org
Subject: Re: [PATCH] x86, apic: Do not increment disabled_cpus from generic_processor_info.
Date: Mon, 10 Jan 2011 12:57:15 +0300	[thread overview]
Message-ID: <4D2AD7FB.8030906@gmail.com> (raw)
In-Reply-To: <AANLkTinM0P90w6tRaogEm1S6o3Prb3DFHNgqgmVTLh+H@mail.gmail.com>

On 01/10/2011 07:06 AM, Rakib Mullick wrote:
> On Mon, Jan 10, 2011 at 12:38 AM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>> On 01/09/2011 07:57 PM, Rakib Mullick wrote:
>>> On Sun, Jan 9, 2011 at 3:39 PM, Ingo Molnar <mingo@elte.hu> wrote:
>>
>>  When nr_cpus=n passed from command line and there is N > n physical cpu
>> present we *still* have to increment disabled_cpus in generic_processor_info
>> because:
>>
>> 1) We're priting out the number of cpu which is disabled
>> 2) total_cpus become inconsistent
>>
>> and while (1) is not that important, total_cpus _is_ important (it
>> is used to print out offlined cpus).
>>
> When we use nr_cpus=n, it works as an upper limit. If there are any
> other CPUs beyond that limit those are not counted and we couldn't put
> them back on work. So, when we couldn't use hotpluging feature to back
> them into work, should we care about them?
> 

  Yes we should, the cpus which are present but offlined (due to maxcpus
or whatever reason) are listed in sysfs so i fear such a change would
break compatibility with userspace as well.

  Rakib, don't get me wrong, I don't like to complain but the side effect
of the patch might be pretty inconvenient.

> 
>>  So I still fail to see why we need to drop the former increment in
>> first place.

-- 
    Cyrill

  reply	other threads:[~2011-01-10  9:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-09  6:29 [PATCH] x86, apic: Do not increment disabled_cpus from generic_processor_info Rakib Mullick
2011-01-09  9:39 ` Ingo Molnar
2011-01-09 11:44   ` Cyrill Gorcunov
2011-01-09 17:09     ` Rakib Mullick
2011-01-09 16:57   ` Rakib Mullick
2011-01-09 18:38     ` Cyrill Gorcunov
2011-01-10  4:06       ` Rakib Mullick
2011-01-10  9:57         ` Cyrill Gorcunov [this message]
2011-01-10 14:04           ` Rakib Mullick

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=4D2AD7FB.8030906@gmail.com \
    --to=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rakib.mullick@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.