summaryrefslogtreecommitdiff
path: root/kexec/arch/ia64/kexec-ia64.c
diff options
context:
space:
mode:
authorSachin P. Sant <sachinp@in.ibm.com>2007-01-23 20:12:33 +0530
committerSimon Horman <horms@verge.net.au>2007-01-29 16:54:29 +0900
commitf8afe9befb4918853b3002725e53ddbbd43cf719 (patch)
treea1fc121f0b2702b14147067f3702a38ea6c4dd17 /kexec/arch/ia64/kexec-ia64.c
parent7792798a79b78a5d566f70c9f00237d050b01350 (diff)
cp /proc/vmcore fails on core generated using latest kexec tools.
* On ppc64 memory ranges in device-tree is denoted as start and size. * While in case of other architectures like i386 it is represented as start and * end. Because of this when loading the memory ranges in crashdump-elf.c the * filesz calculation using start and end values of memory range goes for a toss. * * phdr->p_filesz = phdr->p_memsz = mend - mstart + 1; * * Because of the +1 in above statement the generated vmcore is not a valid * dump file. * * There are different ways in which this problem can be fixed. * A. Add a ifdef in crashdump-elf.c for elf machine type. * if EM_PPC64 then * filesz = end - start; * else * filesz = end - start + 1; * fi * B. Change the ppc64 specific code so as to follow the i386 convention when * it comes to representing memory ranges. * C. Create a PPC64 specific function to populate crash ranges and not use * the generic function from crashdump-elf.c * * Of all these solutions B is the smallest and works well. Here is a patch * to implement the same. * Signed-off-by : Sachin Sant <sachinp@in.ibm.com> Removed trailing whitespace Signed-off-by : Simon Horman <horms@verge.net.au>
Diffstat (limited to 'kexec/arch/ia64/kexec-ia64.c')
0 files changed, 0 insertions, 0 deletions