diff options
author | Michael Ellerman <mpe@ellerman.id.au> | 2017-07-17 21:19:01 +1000 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-07-17 21:30:32 +1000 |
commit | a70b487b07cf4201bc6702e7f646fa593b23009f (patch) | |
tree | c6a8ab47fb925a86a2f8f2ee5a14c8bce802c137 /arch/arm/mach-pxa/cm-x300.c | |
parent | 01e6a61aceb82e13bec29502a8eb70d9574f97ad (diff) | |
download | linux-a70b487b07cf4201bc6702e7f646fa593b23009f.tar.bz2 |
powerpc/powernv: Fix boot on Power8 bare metal due to opal_configure_cores()
In commit 1c0eaf0f56d6 ("powerpc/powernv: Tell OPAL about our MMU mode
on POWER9"), we added additional flags to the OPAL call to configure
CPUs at boot.
These flags only work on Power9 firmwares, and worse can cause boot
failures on Power8 machines, so we check for CPU_FTR_ARCH_300 (aka POWER9)
before adding the extra flags.
Unfortunately we forgot that opal_configure_cores() is called before
the CPU feature checks are dynamically patched, meaning the check
always returns true.
We definitely need to do something to make the CPU feature checks less
prone to bugs like this, but for now the minimal fix is to use
early_cpu_has_feature().
Reported-and-tested-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Fixes: 1c0eaf0f56d6 ("powerpc/powernv: Tell OPAL about our MMU mode on POWER9")
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/arm/mach-pxa/cm-x300.c')
0 files changed, 0 insertions, 0 deletions