powerpc: Don't setup CPUs with bad status
authorMichael Neuling <mikey@neuling.org>
Fri, 6 Jun 2014 04:28:51 +0000 (14:28 +1000)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 11 Jul 2014 12:33:49 +0000 (13:33 +0100)
commit335a4d5ba599428c32e6bdf726cd7f20553220a9
treeb2b5735a3921c6438cf58adbb6c7a631a76e3622
parentbb262325634570b71c7a3c0c338a2a509d0c9200
powerpc: Don't setup CPUs with bad status

commit 59a53afe70fd530040bdc69581f03d880157f15a upstream.

OPAL will mark a CPU that is guarded as "bad" in the status property of the CPU
node.

Unfortunatley Linux doesn't check this property and will put the bad CPU in the
present map.  This has caused hangs on booting when we try to unsplit the core.

This patch checks the CPU is avaliable via this status property before putting
it in the present map.

Signed-off-by: Michael Neuling <mikey@neuling.org>
Tested-by: Anton Blanchard <anton@samba.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
arch/powerpc/kernel/setup-common.c