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

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: crashdump-x86-kconfig.patch --]
[-- Type: text/x-patch, Size: 975 bytes --]



o config option CONFIG_CRASH_DUMP
o Made it dependent on HIGHMEM. This is required as capture kernel treats the
  previous kernel's memory as high memmory and stitches a PTE for accessing
  it.

Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
---

 linux-2.6.12-rc1-mm3-1M-root/arch/i386/Kconfig |    7 +++++++
 1 files changed, 7 insertions(+)

diff -puN arch/i386/Kconfig~crashdump-x86-kconfig arch/i386/Kconfig
--- linux-2.6.12-rc1-mm3-1M/arch/i386/Kconfig~crashdump-x86-kconfig	2005-03-27 18:35:43.000000000 +0530
+++ linux-2.6.12-rc1-mm3-1M-root/arch/i386/Kconfig	2005-03-27 18:35:43.000000000 +0530
@@ -955,6 +955,13 @@ config KEXEC
 	  support.  As of this writing the exact hardware interface is
 	  strongly in flux, so no good recommendation can be made.
 
+config CRASH_DUMP
+	bool "kernel crash dumps (EXPERIMENTAL)"
+	depends on EMBEDDED
+	depends on EXPERIMENTAL
+	depends on HIGHMEM
+	help
+	  Generate crash dump after being started by kexec.
 endmenu
 
 
_

                 reply	other threads:[~2005-03-28 13:42 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=1112016423.4001.80.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

all inboxes | Powered by JetHome®