All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	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 7/8] doc: update the kdump document
Date: Wed, 12 Aug 2009 08:16:32 +0000	[thread overview]
Message-ID: <20090812081854.5757.88620.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20090812081731.5757.25254.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

WARNING: multiple messages have this Message-ID (diff)
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>,
	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 7/8] doc: update the kdump document
Date: Wed, 12 Aug 2009 04:16:32 -0400	[thread overview]
Message-ID: <20090812081854.5757.88620.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20090812081731.5757.25254.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

  parent reply	other threads:[~2009-08-12  8:16 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12  8:15 [Patch 0/8] V3 Implement crashkernel=auto Amerigo Wang
2009-08-12  8:15 ` Amerigo Wang
2009-08-12  8:15 ` [Patch 1/8] x86: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-12  8:15   ` Amerigo Wang
2009-08-12  8:15 ` [Patch 2/8] x86: implement crashkernel=auto Amerigo Wang
2009-08-12  8:15   ` Amerigo Wang
2009-08-12  8:15 ` [Patch 3/8] ia64: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-12  8:15   ` Amerigo Wang
2009-08-12  8:15 ` [Patch 4/8] ia64: implement crashkernel=auto Amerigo Wang
2009-08-12  8:15   ` Amerigo Wang
2009-08-12  8:16 ` [Patch 5/8] powerpc: add CONFIG_KEXEC_AUTO_RESERVE Amerigo Wang
2009-08-12  8:16   ` Amerigo Wang
2009-08-12  8:16 ` [Patch 6/8] powerpc: implement crashkernel=auto Amerigo Wang
2009-08-12  8:16   ` Amerigo Wang
2009-08-12  8:16 ` Amerigo Wang [this message]
2009-08-12  8:16   ` [Patch 7/8] doc: update the kdump document Amerigo Wang
2009-08-12  8:16 ` [Patch 8/8] kexec: allow to shrink reserved memory Amerigo Wang
2009-08-12  8:16   ` Amerigo Wang
2009-08-13  3:11   ` Eric W. Biederman
2009-08-13  3:11     ` Eric W. Biederman
2009-08-13  3:32     ` Amerigo Wang
2009-08-13  3:32       ` Amerigo Wang
2009-08-13  3:32       ` Amerigo Wang
2009-08-13  6:18       ` Eric W. Biederman
2009-08-13  6:18         ` Eric W. Biederman
2009-08-13  6:18         ` Eric W. Biederman
2009-08-13  8:23         ` Amerigo Wang
2009-08-13  8:23           ` Amerigo Wang
2009-08-13  8:23           ` Amerigo Wang
2009-08-14 22:17           ` Eric W. Biederman
2009-08-14 22:17             ` Eric W. Biederman
2009-08-14 22:17             ` Eric W. Biederman
2009-08-17  9:50             ` Amerigo Wang
2009-08-17  9:50               ` Amerigo Wang
2009-08-17  9:50               ` Amerigo Wang
2009-08-18  0:29               ` KAMEZAWA Hiroyuki
2009-08-18  0:29                 ` KAMEZAWA Hiroyuki
2009-08-18  0:29                 ` KAMEZAWA Hiroyuki
2009-08-18  6:31                 ` Amerigo Wang
2009-08-18  6:31                   ` Amerigo Wang
2009-08-18  6:31                   ` Amerigo Wang
2009-08-18  8:25                   ` KAMEZAWA Hiroyuki
2009-08-18  8:25                     ` KAMEZAWA Hiroyuki
2009-08-18  8:25                     ` KAMEZAWA Hiroyuki
2009-08-18  8:51                     ` Amerigo Wang
2009-08-18  8:51                       ` Amerigo Wang
2009-08-18  8:51                       ` Amerigo Wang
2009-08-18 10:35                     ` Amerigo Wang
2009-08-18 10:35                       ` Amerigo Wang
2009-08-18 10:35                       ` Amerigo Wang
2009-08-18 23:57                       ` KAMEZAWA Hiroyuki
2009-08-18 23:57                         ` KAMEZAWA Hiroyuki
2009-08-18 23:57                         ` KAMEZAWA Hiroyuki
2009-08-19  2:41                         ` Amerigo Wang
2009-08-19  2:41                           ` Amerigo Wang
2009-08-19  2:41                           ` Amerigo Wang
2009-08-19  8:13                           ` KAMEZAWA Hiroyuki
2009-08-19  8:13                             ` KAMEZAWA Hiroyuki
2009-08-19  8:13                             ` KAMEZAWA Hiroyuki
2009-08-19 10:47                             ` Amerigo Wang
2009-08-19 10:47                               ` Amerigo Wang
2009-08-19 10:47                               ` Amerigo Wang
2009-08-20  9:15                             ` Amerigo Wang
2009-08-20  9:15                               ` Amerigo Wang
2009-08-20  9:15                               ` Amerigo Wang
2009-08-21  0:34                               ` KAMEZAWA Hiroyuki
2009-08-21  0:34                                 ` KAMEZAWA Hiroyuki
2009-08-21  0:34                                 ` KAMEZAWA Hiroyuki
2009-08-21  1:59                                 ` Amerigo Wang
2009-08-21  1:59                                   ` Amerigo Wang
2009-08-21  1:59                                   ` Amerigo Wang
2009-08-21  2:03                                   ` KAMEZAWA Hiroyuki
2009-08-21  2:03                                     ` KAMEZAWA Hiroyuki
2009-08-21  2:03                                     ` KAMEZAWA Hiroyuki
2009-08-21  2:47                                     ` Amerigo Wang
2009-08-21  2:47                                       ` Amerigo Wang
2009-08-21  2:47                                       ` Amerigo Wang
2009-08-12 12:46 ` [Patch 0/8] V3 Implement crashkernel=auto Bernhard Walle
2009-08-12 12:46   ` Bernhard Walle
2009-08-13  2:49   ` Amerigo Wang
2009-08-13  2:49     ` Amerigo Wang
2009-08-13  5:39     ` Bernhard Walle
2009-08-13  5:39       ` Bernhard Walle
2009-08-13  8:19       ` Amerigo Wang
2009-08-13  8:19         ` Amerigo Wang
2009-08-13  9:03         ` Bernhard Walle
2009-08-13  9:03           ` Bernhard Walle
2009-08-13 10:49           ` Eric W. Biederman
2009-08-13 10:49             ` Eric W. Biederman
2009-08-14  2:59             ` Amerigo Wang
2009-08-14  2:59               ` Amerigo Wang
  -- strict thread matches above, loose matches on Subject: below --
2009-08-27  3:15 [Patch 0/8] V5 " Amerigo Wang
2009-08-27  3:16 ` [Patch 7/8] doc: update the kdump document Amerigo Wang
2009-08-27  3:16   ` Amerigo Wang
2009-09-04 10:08 [Patch 0/8] V6 Implement crashkernel=auto Amerigo Wang
2009-09-04 10:09 ` [Patch 7/8] doc: update the kdump document Amerigo Wang
2009-09-04 10:09   ` 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=20090812081854.5757.88620.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.