[RFC/PATCH 0/17][Kdump] Overview

[Vivek Goyal <vgoyal@in.ibm.com>]

Hi,

This patchset restores back the kdump functionality on i386. Patchset
contains the patches for user space (kexec-tools-1.101) and kernel space
(2.6.12-rc1-mm3). Some of the user space patches are being released for
the completeness.

This patch set performs following.

kexec-tool-1.101
(http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz)
-----------------------------------------------------------------------

- Create a backup region and copy the first 640K of memory to backup
  region over a crash.
- Generate Elf headers representing crashed memory and store in reserved
  region. Also appends the memmap= and elfcorehdr= parameters to command
  line internally to be passed to capture kernel.
- Fills in the virtual addresses for linearly mapped region at the elf
  header creation time. This assists in limited debugging through gdb.
- Adds another command line option "--crash-dump" to differentiate
  between kexec on panic and kexec on panic with crash dump on.


2.6.12-rc1-mm3
--------------

- Retrieve physical address of elf core headers, stored by crashed
  kernel.
- Export dump image in ELF format through /proc/vmcore interface.
- Export raw dump image through /dev/oldmem interface.


Following patches (as in series file) need to be dropped before applying
the fresh ones.

crashdump-documentation.patch
crashdump-memory-preserving-reboot-using-kexec.patch
crashdump-routines-for-copying-dump-pages.patch
crashdump-routines-for-copying-dump-pages-fixes.patch
crashdump-elf-format-dump-file-access.patch
crashdump-linear-raw-format-dump-file-access.patch
crashdump-linear-raw-format-dump-file-access-coding-style.patch


I look forward for comments and suggestions. I have done basic testing
on uni and SMP systems.

Thanks
Vivek

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/