diff options
author | Suzuki Poulose | 2012-08-21 01:42:43 +0000 |
---|---|---|
committer | Benjamin Herrenschmidt | 2012-09-07 11:44:33 +1000 |
commit | 4bc77a5ed215b4ec9cc39d5f55323b2e68000055 (patch) | |
tree | e1735aea84fe497b4f9359a391e2cc2f842243c1 /security | |
parent | a84fcd46870113e92523e1ebb9a0ec75f66e03a2 (diff) |
powerpc: Export memory limit via device tree
The powerpc kernel doesn't export the memory limit enforced by 'mem='
kernel parameter. This is required for building the ELF header in
kexec-tools to limit the vmcore to capture only the used memory. On
powerpc the kexec-tools depends on the device-tree for memory related
information, unlike /proc/iomem on the x86.
Without this information, the kexec-tools assumes the entire System
RAM and vmcore creates an unnecessarily larger dump.
This patch exports the memory limit, if present, via
chosen/linux,memory-limit
property, so that the vmcore can be limited to the memory limit.
The prom_init seems to export this value in the same node. But doesn't
really
appear there. Also the memory_limit gets adjusted with the processing of
crashkernel= parameter. This patch makes sure we get the actual limit.
The kexec-tools will use the value to limit the 'end' of the memory
regions.
Tested this patch on ppc64 and ppc32(ppc440) with a kexec-tools
patch by Mahesh.
Signed-off-by: Suzuki K. Poulose <suzuki@in.ibm.com>
Tested-by: Mahesh J. Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions