linux-kernel - Re: [patch x86/core] x86: allow number of additional hotplug CPUs to be set at compile time

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: <20081002152521.16c4835b@redhat.com>
Date:	Thu, 2 Oct 2008 15:25:21 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [patch x86/core] x86: allow number of additional hotplug CPUs
 to be set at compile time

On Thu, 02 Oct 2008 11:12:51 +0200
Andi Kleen <andi@...stfloor.org> wrote:

> Chuck Ebbert <cebbert@...hat.com> writes:
> 
> > The default number of additional CPU IDs for hotplugging is determined
> > by asking ACPI or mptables how many "disabled" CPUs there are in the
> > system, but many systems get this wrong so that e.g. a uniprocessor
> > machine gets an extra CPU allocated and never switches to single CPU
> > mode.
> 
> You can set this with additional_cpus=... at boot time.
> I don't think each runtime option needs a CONFIG option too.
> 

Well not all of them, but this one is a good candidate.  Either that or
we should just change the default to zero.
--
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/