mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: fastboot <fastboot@lists.osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: [RFC][PATCH 0/3] Kdump: Overview
Date: 24 Feb 2005 21:45:49 +0530	[thread overview]
Message-ID: <1109261749.5148.807.camel@terminator.in.ibm.com> (raw)

Hi,

Following set of patches go one step ahead in restoring the broken kdump
functionality in -mm tree on x86. Most of the kdump functionality has
now moved to kexec user space (kexec-tools).

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.


2.6.11-rc4-mm1
--------------
- Export address of start of crash notes section (crash_notes) to user
  space through sysfs

I look forward for comments and suggestions. I have done basic testing
on uni and 4way (SMT) systems. 


2.6.11-rc4-mm1 does not boot if booted with kexec enabled and
crashkernel=X@Y is passed as command line parameter. Following patch
needs to be applied to rectify the problem.

http://lkml.org/lkml/2005/2/24/51


Thanks
Vivek


                 reply	other threads:[~2005-02-24 15:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1109261749.5148.807.camel@terminator.in.ibm.com \
    --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

all inboxes | Powered by JetHome®