diff options
author | Gautham R. Shenoy <ego@linux.vnet.ibm.com> | 2017-08-31 17:17:41 +0530 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-09-20 13:30:09 +1000 |
commit | 5d298baa41883fc421acfd932799c0f4177249ae (patch) | |
tree | adc0c98a8a7f50cb457bc2525e4a6cb94e81ddfd /arch/powerpc/kernel/traps.c | |
parent | 1575fe06f6b1d156ed31fb22c8631d49d79751d8 (diff) | |
download | linux-5d298baa41883fc421acfd932799c0f4177249ae.tar.gz linux-5d298baa41883fc421acfd932799c0f4177249ae.tar.bz2 linux-5d298baa41883fc421acfd932799c0f4177249ae.zip |
powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline
Commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via
stop-api only on Hotplug") clears the PECE1 bit of the LPCR via
stop-api during CPU-Hotplug to prevent wakeup due to a decrementer on
an offlined CPU which is in a deep stop state.
In the case where the stop-api support is found to be lacking, the
commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT
states when stop-api fails") disables deep states that lose hypervisor
context. Thus in this case, the offlined CPU will be put to some
shallow idle state.
However, we currently unconditionally clear the PECE1 in LPCR via
stop-api during CPU-Hotplug even when deep states are disabled due to
stop-api failure.
Fix this by clearing PECE1 of LPCR via stop-api during CPU-Hotplug
*only* when the offlined CPU will be put to a deep state that loses
hypervisor context.
Fixes: 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api only on Hotplug")
Reported-by: Pavithra Prakash <pavirampu@linux.vnet.ibm.com>
Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Tested-by: Pavithra Prakash <pavrampu@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/kernel/traps.c')
0 files changed, 0 insertions, 0 deletions