From: Amerigo Wang <amwang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org,
Neil Horman <nhorman@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
kamezawa.hiroyu@jp.fujitsu.com, Andi Kleen <andi@firstfloor.org>,
Amerigo Wang <amwang@redhat.com>,
akpm@linux-foundation.org, bernhard.walle@gmx.de,
Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@elte.hu>,
Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: [Patch 8/8] doc: update the kdump document
Date: Fri, 21 Aug 2009 02:55:34 -0400 [thread overview]
Message-ID: <20090821065759.4855.24212.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20090821065637.4855.32234.sendpatchset@localhost.localdomain>
Update the document for kdump.
Signed-off-by: WANG Cong <amwang@redhat.com>
---
Index: linux-2.6/Documentation/kdump/kdump.txt
===================================================================
--- linux-2.6.orig/Documentation/kdump/kdump.txt
+++ linux-2.6/Documentation/kdump/kdump.txt
@@ -147,6 +147,15 @@ System kernel config options
analysis tools require a vmlinux with debug symbols in order to read
and analyze a dump file.
+4) Enable "automatically reserve memory for kexec kernel" in
+ "Processor type and features."
+
+ CONFIG_KEXEC_AUTO_RESERVE=y
+
+ This will let you to use "crashkernel=auto", instead of specifying
+ numbers for "crashkernel=". Note, you need to have enough memory.
+ The threshold and reserved memory size are arch-dependent.
+
Dump-capture kernel config options (Arch Independent)
-----------------------------------------------------
@@ -266,6 +275,25 @@ This would mean:
2) if the RAM size is between 512M and 2G (exclusive), then reserve 64M
3) if the RAM size is larger than 2G, then reserve 128M
+Or you can use:
+
+ crashkernel=auto
+
+if you have enough memory. The threshold is 4G, below which this won't work.
+
+The automatically reserved memory size would be 128M on x86_32, 256M on
+ppc, 1/32 of your physical memory size on x86_64 and ppc64 (but it will not
+exceed 1TB/32 if you have more). IA64 has its own policy, shown below:
+
+ Memory size Reserved memory
+ =========== ===============
+ [4G, 12G) 256M
+ [12G, 128G) 512M
+ [128G, 256G) 768M
+ [256G, 378G) 1024M
+ [378G, 512G) 1536M
+ [512G, 768G) 2048M
+ [768G, ) 3072M
Boot into System Kernel
next prev parent reply other threads:[~2009-08-21 6:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:54 [Patch 0/8] V4 Implement crashkernel=auto Amerigo Wang
2009-08-21 6:54 ` [Patch 1/8] kexec: allow to shrink reserved memory Amerigo Wang
2009-08-22 0:17 ` Andrew Morton
2009-08-24 1:36 ` Amerigo Wang
2009-08-22 1:39 ` Eric W. Biederman
2009-08-24 2:02 ` Amerigo Wang
2009-08-21 6:54 ` [Patch 2/8] x86: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-21 6:54 ` [Patch 3/8] x86: implement crashkernel=auto Amerigo Wang
2009-08-21 6:54 ` [Patch 4/8] ia64: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-21 6:55 ` [Patch 5/8] ia64: implement crashkernel=auto Amerigo Wang
2009-08-22 0:24 ` Andrew Morton
2009-08-22 11:18 ` Ingo Molnar
2009-08-24 2:05 ` Amerigo Wang
2009-08-24 7:43 ` Ingo Molnar
2009-08-24 8:21 ` Bernhard Walle
2009-08-24 10:23 ` Amerigo Wang
2009-08-24 1:59 ` Amerigo Wang
2009-08-21 6:55 ` [Patch 6/8] powerpc: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-24 13:44 ` Michael Ellerman
2009-08-24 14:45 ` M. Mohan Kumar
2009-08-25 6:37 ` Amerigo Wang
2009-08-25 10:24 ` M. Mohan Kumar
2009-08-25 6:23 ` Amerigo Wang
2009-08-25 10:28 ` M. Mohan Kumar
2009-08-26 6:59 ` Amerigo Wang
2009-08-21 6:55 ` [Patch 7/8] powerpc: implement crashkernel=auto Amerigo Wang
2009-08-21 6:55 ` Amerigo Wang [this message]
2009-08-22 0:06 ` [Patch 0/8] V4 Implement crashkernel=auto Andrew Morton
2009-08-24 1:34 ` Amerigo Wang
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=20090821065759.4855.24212.sendpatchset@localhost.localdomain \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=avorontsov@ru.mvista.com \
--cc=bernhard.walle@gmx.de \
--cc=ebiederm@xmission.com \
--cc=fenghua.yu@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@redhat.com \
--cc=tony.luck@intel.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