summaryrefslogtreecommitdiffstats
path: root/.mailmap
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2010-06-07 15:34:38 +0000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2010-06-15 15:02:32 +1000
commitb5416ca9f824d3deb1e25a32683100360e104b72 (patch)
treec5f383b7fbc3e22d614c48663b4618214b06ba7a /.mailmap
parent8054a3428fbec2d91dfeb5bd78d7e75064cf163b (diff)
downloadblackbird-op-linux-b5416ca9f824d3deb1e25a32683100360e104b72.tar.gz
blackbird-op-linux-b5416ca9f824d3deb1e25a32683100360e104b72.zip
powerpc: Move kdump default base address to 64MB on 64bit
We are seeing boot fails on some System p machines when using the kdump crashkernel= boot option. The default kdump base address is 32MB, so if we reserve 256MB for kdump then we reserve all of the RMO except the first 32MB. We really want kdump to reserve some memory in the RMO and most of it elsewhere but that will require more significant changes. For now we can shift the default base address to 64MB when CONFIG_PPC64 and CONFIG_RELOCATABLE are set. This isn't quite correct since what we really care about is the kdump kernel is relocatable, but we already make the assumption that base kernel and kdump kernel have the same CONFIG_RELOCATABLE setting, eg: #ifndef CONFIG_RELOCATABLE if (crashk_res.start != KDUMP_KERNELBASE) printk("Crash kernel location must be 0x%x\n", KDUMP_KERNELBASE); ... RTAS is instantiated towards the top of our RMO, so if we were to go any higher we risk not having enough RMO memory for the kdump kernel on boxes with a 128MB RMO. Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud