aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/cpuidle
diff options
context:
space:
mode:
authorGautham R. Shenoy <ego@linux.vnet.ibm.com>2017-05-16 14:19:47 +0530
committerMichael Ellerman <mpe@ellerman.id.au>2017-05-30 14:59:51 +1000
commit22c6663dc69a042a7b4158f162582b4b1ba7a4b7 (patch)
tree0e67968c50a9359fc84ee0ef1cba7b546988528c /drivers/cpuidle
parentpowerpc/powernv/idle: Restore SPRs for deep idle states via stop API. (diff)
downloadlinux-dev-22c6663dc69a042a7b4158f162582b4b1ba7a4b7.tar.xz
linux-dev-22c6663dc69a042a7b4158f162582b4b1ba7a4b7.zip
powerpc/powernv/idle: Use Requested Level for restoring state on P9 DD1
On Power9 DD1 due to a hardware bug the Power-Saving Level Status field (PLS) of the PSSCR for a thread waking up from a deep state can under-report if some other thread in the core is in a shallow stop state. The scenario in which this can manifest is as follows: 1) All the threads of the core are in deep stop. 2) One of the threads is woken up. The PLS for this thread will correctly reflect that it is waking up from deep stop. 3) The thread that has woken up now executes a shallow stop. 4) When some other thread in the core is woken, its PLS will reflect the shallow stop state. Thus, the subsequent thread for which the PLS is under-reporting the wakeup state will not restore the hypervisor resources. Hence, on DD1 systems, use the Requested Level (RL) field as a workaround to restore the contents of the hypervisor resources on the wakeup from the stop state. Signed-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'drivers/cpuidle')
0 files changed, 0 insertions, 0 deletions