mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>, fastboot <fastboot@lists.osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: [RFC/PATCH 0/17][Kdump] Overview
Date: Mon, 28 Mar 2005 18:55:41 +0530	[thread overview]
Message-ID: <1112016341.4001.71.camel@localhost.localdomain> (raw)

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


             reply	other threads:[~2005-03-28 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 13:25 Vivek Goyal [this message]
2005-03-29  1:48 ` Andrew Morton
2005-03-29  4:59   ` Vivek Goyal
2005-03-29  7:13     ` [Fastboot] " Suparna Bhattacharya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1112016341.4001.71.camel@localhost.localdomain \
    --to=vgoyal@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome