linux-kernel - Re: [PATCH] add command line init_start

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]

Date:	Sun, 14 Dec 2008 19:39:48 -0800
From:	"Yinghai Lu" <yinghai@...nel.org>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] add command line init_start_cpus

On Sun, Dec 14, 2008 at 4:11 PM, Andi Kleen <andi@...stfloor.org> wrote:
> Yinghai Lu <yinghai@...nel.org> writes:
>
>> Impact: new command line
>>
>> so could select cpus to be started during init stage
>
> maxcpus=N should do this already, at least for the first N cpus.
> If you really need a non continuous range of N (why?) then it would
> be better to fix maxcpus instead of adding a new option.

it seems it is hard to make maxcpus= to support random cpus selecting and
maxcpus=0 looks insane

also maxcpus=1, will disable smp, can you enable other cpus later in user space?

YH
--
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/