Gitweb:
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ee8bb9eae66d3d5558b685f71b52bd8bc4ba5a62
Commit: ee8bb9eae66d3d5558b685f71b52bd8bc4ba5a62
Parent: ea112bd5493d44967b3dc44fd078be517272b044
Author: Horms [EMAIL PROTECTED]
AuthorDate: Mon Jan 22 20:40:49 2007 -0800
Committer: Linus Torvalds [EMAIL PROTECTED]
CommitDate: Tue Jan 23 07:52:07 2007 -0800
[PATCH] Kdump documentation update: ia64 portion
this patch fills in the portions for ia64 kexec.
Signed-off-by: Simon Horman [EMAIL PROTECTED]
Cc: Zou, Nanhai [EMAIL PROTECTED]
Cc: Vivek Goyal [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
Signed-off-by: Linus Torvalds [EMAIL PROTECTED]
---
Documentation/kdump/kdump.txt | 36 +---
1 files changed, 29 insertions(+), 7 deletions(-)
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index 2e5b317..0733068 100644
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -17,7 +17,7 @@ You can use common Linux commands, such as cp and scp, to
copy the
memory image to a dump file on the local disk, or across the network to
a remote system.
-Kdump and kexec are currently supported on the x86, x86_64, ppc64 and IA64
+Kdump and kexec are currently supported on the x86, x86_64, ppc64 and ia64
architectures.
When the system kernel boots, it reserves a small section of memory for
@@ -229,7 +229,23 @@ Dump-capture kernel config options (Arch Dependent, ppc64)
Dump-capture kernel config options (Arch Dependent, ia64)
--
-(To be filled)
+
+- No specific options are required to create a dump-capture kernel
+ for ia64, other than those specified in the arch idependent section
+ above. This means that it is possible to use the system kernel
+ as a dump-capture kernel if desired.
+
+ The crashkernel region can be automatically placed by the system
+ kernel at run time. This is done by specifying the base address as 0,
+ or omitting it all together.
+
+ [EMAIL PROTECTED]
+ or
+ crashkernel=256M
+
+ If the start address is specified, note that the start address of the
+ kernel will be aligned to 64Mb, so if the start address is not then
+ any space below the alignment point will be wasted.
Boot into System Kernel
@@ -248,6 +264,10 @@ Boot into System Kernel
On ppc64, use [EMAIL PROTECTED].
+ On ia64, [EMAIL PROTECTED] is a generous value that typically works.
+ The region may be automatically placed on ia64, see the
+ dump-capture kernel config option notes above.
+
Load the Dump-capture Kernel
@@ -266,7 +286,8 @@ For x86_64:
For ppc64:
- Use vmlinux
For ia64:
- (To be filled)
+ - Use vmlinux or vmlinuz.gz
+
If you are using a uncompressed vmlinux image then use following command
to load dump-capture kernel.
@@ -282,18 +303,19 @@ to load dump-capture kernel.
--initrd=initrd-for-dump-capture-kernel \
--append=root=root-dev arch-specific-options
+Please note, that --args-linux does not need to be specified for ia64.
+It is planned to make this a no-op on that architecture, but for now
+it should be omitted
+
Following are the arch specific command line options to be used while
loading dump-capture kernel.
-For i386 and x86_64:
+For i386, x86_64 and ia64:
init 1 irqpoll maxcpus=1
For ppc64:
init 1 maxcpus=1 noirqdistrib
-For IA64
- (To be filled)
-
Notes on loading the dump-capture kernel:
-
To unsubscribe from this list: send the line unsubscribe git-commits-head in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
