summaryrefslogtreecommitdiffstats
path: root/arch/avr32/configs/atngw100mkii_evklcd100_defconfig
diff options
context:
space:
mode:
authorMahesh Salgaonkar <mahesh@linux.vnet.ibm.com>2013-12-09 15:33:39 +0530
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2013-12-10 11:28:39 +1100
commite641eb03ab2b0f065fa5e64b4202fb5b0441b427 (patch)
tree3c92bfb8705a637fcd1b317d851ac089d7ac7eb5 /arch/avr32/configs/atngw100mkii_evklcd100_defconfig
parent08607afba64cc7a14d22b8aa2837d00f1d877d83 (diff)
downloadlinux-e641eb03ab2b0f065fa5e64b4202fb5b0441b427.tar.gz
linux-e641eb03ab2b0f065fa5e64b4202fb5b0441b427.tar.xz
powerpc: Fix up the kdump base cap to 128M
The current logic sets the kdump base to min of 2G or ppc64_rma_size/2. On PowerNV kernel the first memory block 'memory@0' can be very large, equal to the DIMM size with ppc64_rma_size value capped to 1G. Hence on PowerNV, kdump base is set to 512M resulting kdump to fail while allocating paca array. This is because, paca need its memory from RMA region capped at 256M (see allocate_pacas()). This patch lowers the kdump base cap to 128M so that kdump kernel can successfully get memory below 256M for paca allocation. Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/avr32/configs/atngw100mkii_evklcd100_defconfig')
0 files changed, 0 insertions, 0 deletions