diff options
author | Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com> | 2014-01-31 00:31:04 +0530 |
---|---|---|
committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2014-02-11 11:24:47 +1100 |
commit | 429d2e8342954d337abe370d957e78291032d867 (patch) | |
tree | 291d3bcb329161fd4d92faa3286cd604062c2319 /arch/powerpc/kernel/reloc_64.S | |
parent | 3ec8b78fcc5aa7745026d8d85a4e9ab52c922765 (diff) | |
download | linux-429d2e8342954d337abe370d957e78291032d867.tar.bz2 |
powerpc: Fix kdump hang issue on p8 with relocation on exception enabled.
On p8 systems, with relocation on exception feature enabled we are seeing
kdump kernel hang at interrupt vector 0xc*4400. The reason is, with this
feature enabled, exception are raised with MMU (IR=DR=1) ON with the
default offset of 0xc*4000. Since exception is raised in virtual mode it
requires the vector region to be executable without which it fails to
fetch and execute instruction at 0xc*4xxx. For default kernel since kernel
is loaded at real 0, the htab mappings sets the entire kernel text region
executable. But for relocatable kernel (e.g. kdump case) we only copy
interrupt vectors down to real 0 and never marked that region as
executable because in p7 and below we always get exception in real mode.
This patch fixes this issue by marking htab mapping range as executable
that overlaps with the interrupt vector region for relocatable kernel.
Thanks to Ben who helped me to debug this issue and find the root cause.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/powerpc/kernel/reloc_64.S')
0 files changed, 0 insertions, 0 deletions