From: linas@austin.ibm.com (Linas Vepstas)
To: linuxppc-dev@ozlabs.org
Cc: mahuja@us.ibm.com, lkessler@us.ibm.com, strosake@us.ibm.com,
mahuja@austin.ibm.com
Subject: [PATCH/RFC 2/6]: phyp dump: config file
Date: Wed, 21 Nov 2007 16:39:20 -0600 [thread overview]
Message-ID: <20071121223920.GB26122@austin.ibm.com> (raw)
In-Reply-To: <20071121223639.GB4374@austin.ibm.com>
Add hypervisor-assisted dump to kernel config
Signed-off-by: Linas Vepstas <linas@austin.ibm.com>
-----
arch/powerpc/Kconfig | 11 +++++++++++
1 file changed, 11 insertions(+)
Index: linux-2.6.24-rc2-git4/arch/powerpc/Kconfig
===================================================================
--- linux-2.6.24-rc2-git4.orig/arch/powerpc/Kconfig 2007-11-14 16:39:20.000000000 -0600
+++ linux-2.6.24-rc2-git4/arch/powerpc/Kconfig 2007-11-15 14:27:33.000000000 -0600
@@ -261,6 +261,17 @@ config CRASH_DUMP
Don't change this unless you know what you are doing.
+config PHYP_DUMP
+ bool "Hypervisor-assisted dump (EXPERIMENTAL)"
+ depends on PPC_PSERIES && EXPERIMENTAL
+ default y
+ help
+ Hypervisor-assisted dump is meant to be a kdump replacement
+ offering robustness and speed not possible without system
+ hypervisor assistence.
+
+ If unsure, say "Y"
+
config PPCBUG_NVRAM
bool "Enable reading PPCBUG NVRAM during boot" if PPLUS || LOPEC
default y if PPC_PREP
next prev parent reply other threads:[~2007-11-21 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 22:36 [PATCH/RFC 0/6]: phyp dump: hypervisor-assisted dump Linas Vepstas
2007-11-21 22:37 ` [PATCH/RFC 1/6]: phyp dump: Documentation Linas Vepstas
2007-11-21 22:39 ` Linas Vepstas [this message]
2007-11-21 22:40 ` [PATCH/RFC 3/6]: phyp dump: reserve-release proof-of-concept Linas Vepstas
2007-11-21 22:41 ` [PATCH/RFC 4/6]: phyp dump: use sysfs to release reserved mem Linas Vepstas
2007-11-21 22:43 ` [PATCH/RFC 5/6]: phyp dump: register the dump area Linas Vepstas
2007-11-21 22:45 ` [PATCH/RFC 6/6]: phyp dump: debugging print routines Linas Vepstas
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=20071121223920.GB26122@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=lkessler@us.ibm.com \
--cc=mahuja@austin.ibm.com \
--cc=mahuja@us.ibm.com \
--cc=strosake@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).