linux-kernel - Re: [PATCH] x86, apic: Do not increment disabled_cpus from generic_processor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinM0P90w6tRaogEm1S6o3Prb3DFHNgqgmVTLh+H@mail.gmail.com>
Date:	Mon, 10 Jan 2011 10:06:21 +0600
From:	Rakib Mullick <rakib.mullick@...il.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>, x86@...nel.org
Subject: Re: [PATCH] x86, apic: Do not increment disabled_cpus from generic_processor_info.

On Mon, Jan 10, 2011 at 12:38 AM, Cyrill Gorcunov <gorcunov@...il.com> wrote:
> On 01/09/2011 07:57 PM, Rakib Mullick wrote:
>> On Sun, Jan 9, 2011 at 3:39 PM, Ingo Molnar <mingo@...e.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?


>  So I still fail to see why we need to drop the former increment in
> first place.
> --
>    Cyrill
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/