summaryrefslogtreecommitdiffstats
path: root/Documentation/fb/gxfb.txt
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@samba.org>2014-12-10 00:26:50 +0530
committerMichael Ellerman <mpe@ellerman.id.au>2014-12-15 10:46:32 +1100
commit8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0 (patch)
tree5a241a94c1ebbfce37287e753c45404b6b0bbded /Documentation/fb/gxfb.txt
parent470834508f87877f680738a10a305280582c7aed (diff)
downloadop-kernel-dev-8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0.zip
op-kernel-dev-8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0.tar.gz
powerpc/powernv: Switch off MMU before entering nap/sleep/rvwinkle mode
Currently, when going idle, we set the flag indicating that we are in nap mode (paca->kvm_hstate.hwthread_state) and then execute the nap (or sleep or rvwinkle) instruction, all with the MMU on. This is bad for two reasons: (a) the architecture specifies that those instructions must be executed with the MMU off, and in fact with only the SF, HV, ME and possibly RI bits set, and (b) this introduces a race, because as soon as we set the flag, another thread can switch the MMU to a guest context. If the race is lost, this thread will typically start looping on relocation-on ISIs at 0xc...4400. This fixes it by setting the MSR as required by the architecture before setting the flag or executing the nap/sleep/rvwinkle instruction. Cc: stable@vger.kernel.org [ shreyas@linux.vnet.ibm.com: Edited to handle LE ] Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Shreyas B. Prabhu <shreyas@linux.vnet.ibm.com> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Michael Ellerman <mpe@ellerman.id.au> Cc: linuxppc-dev@lists.ozlabs.org Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'Documentation/fb/gxfb.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud