linux-kernel - Re: [PATCH v4 5/5] arm64: Fix behavior of maxcpus=N

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] [day] [month] [year] [list]

Message-ID: <20160422135014.GM2998@e104818-lin.cambridge.arm.com>
Date:	Fri, 22 Apr 2016 14:50:15 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Suzuki K Poulose <suzuki.poulose@....com>
Cc:	linux-arm-kernel@...ts.infradead.org, mark.rutland@....com,
	marc.zyngier@....com, will.deacon@....com,
	linux-kernel@...r.kernel.org, James Morse <james.morse@....com>,
	Vadim.Lomovtsev@...iumnetworks.com
Subject: Re: [PATCH v4 5/5] arm64: Fix behavior of maxcpus=N

On Fri, Apr 22, 2016 at 12:25:35PM +0100, Suzuki K. Poulose wrote:
> maxcpu=n sets the number of CPUs activated at boot time to a max of n,
> but allowing the remaining CPUs to be brought up later if the user
> decides to do so. However, on arm64 due to various reasons, we disallowed
> hotplugging CPUs beyond n, by marking them not present. Now that
> we have checks in place to make sure the hotplugged CPUs have compatible
> features with system and requires no new errata, relax the restriction.
> 
> Cc: Will Deacon <will.deacon@....com>
> Cc: Catalin Marinas <catalin.marinas@....com>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: James Morse <james.morse@....com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@....com>

Reviewed-by: Catalin Marinas <catalin.marinas@....com>