powerpc/powernv: Remove the usage of PACAR1 from opal wrappers
authorMahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Sun, 15 May 2016 04:14:13 +0000 (09:44 +0530)
committerPaul Mackerras <paulus@ozlabs.org>
Mon, 20 Jun 2016 04:11:25 +0000 (14:11 +1000)
commit6dd06d15a86e8fca21ed4fb568bed2b3da7a7907
treef2d64b772867024f6772d2d9418ce90944a85558
parentb69890d18fa33a53cec6ae5c93555ee0c24fe0a9
powerpc/powernv: Remove the usage of PACAR1 from opal wrappers

OPAL_CALL wrapper code sticks the r1 (stack pointer) into PACAR1 purely
for debugging purpose only. The power7_wakeup* functions relies on stack
pointer saved in PACAR1. Any opal call made using opal wrapper (directly
or in-directly) before we fall through power7_wakeup*, then it ends up
replacing r1 in PACAR1(r13) leading to kernel panic. So far we don't see
any issues because we have never made any opal calls using OPAL wrapper
before power7_wakeup*. But the subsequent HMI patch would need to invoke
C calls during cpu wakeup/idle path that in-directly makes opal call using
opal wrapper. This patch facilitates the subsequent HMI patch by removing
usage of PACAR1 from opal call wrapper.

Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
arch/powerpc/platforms/powernv/opal-wrappers.S