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: <48E525A1.5080509@zytor.com>
Date:	Thu, 02 Oct 2008 12:48:49 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Chuck Ebbert <cebbert@...hat.com>, linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Li Zefan <lizf@...fujitsu.com>
Subject: Re: [patch x86/core] x86: allow number of additional hotplug CPUs
 to be set at compile time, V2

Ingo Molnar wrote:
>>
>> 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.
>>
>> And sometimes CPU hotplugging is enabled only for suspend/hibernate 
>> anyway, so the additional CPU IDs are not wanted. Allow the number to 
>> be set to zero at compile time.
>>

Wouldn't this be better to have a runtime option?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ