Commit 8bc9d422 authored by Bernhard Walle's avatar Bernhard Walle Committed by Linus Torvalds

Express relocatability of kernel on x86_64 in documentation

This patch adapts the Documentation/kdump/kdump.txt file to express the fact
that the x86_64 kernel is now also relocatable.  This makes i386 and x86_64
now behave the same, simplifying the documentation.
Signed-off-by: default avatarBernhard Walle <bwalle@suse.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Vivek Goyal <vgoyal@in.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Haren Myneni <hbabu@us.ibm.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 98612acd
...@@ -159,16 +159,17 @@ Dump-capture kernel config options (Arch Independent) ...@@ -159,16 +159,17 @@ Dump-capture kernel config options (Arch Independent)
CONFIG_PROC_VMCORE=y CONFIG_PROC_VMCORE=y
(CONFIG_PROC_VMCORE is set by default when CONFIG_CRASH_DUMP is selected.) (CONFIG_PROC_VMCORE is set by default when CONFIG_CRASH_DUMP is selected.)
Dump-capture kernel config options (Arch Dependent, i386) Dump-capture kernel config options (Arch Dependent, i386 and x86_64)
-------------------------------------------------------- --------------------------------------------------------------------
1) On x86, enable high memory support under "Processor type and
1) On i386, enable high memory support under "Processor type and
features": features":
CONFIG_HIGHMEM64G=y CONFIG_HIGHMEM64G=y
or or
CONFIG_HIGHMEM4G CONFIG_HIGHMEM4G
2) On x86 and x86_64, disable symmetric multi-processing support 2) On i386 and x86_64, disable symmetric multi-processing support
under "Processor type and features": under "Processor type and features":
CONFIG_SMP=n CONFIG_SMP=n
...@@ -203,28 +204,6 @@ Dump-capture kernel config options (Arch Dependent, i386) ...@@ -203,28 +204,6 @@ Dump-capture kernel config options (Arch Dependent, i386)
5) Make and install the kernel and its modules. DO NOT add this kernel 5) Make and install the kernel and its modules. DO NOT add this kernel
to the boot loader configuration files. to the boot loader configuration files.
Dump-capture kernel config options (Arch Dependent, x86_64)
----------------------------------------------------------
1) On x86 and x86_64, disable symmetric multi-processing support
under "Processor type and features":
CONFIG_SMP=n
(If CONFIG_SMP=y, then specify maxcpus=1 on the kernel command line
when loading the dump-capture kernel, see section "Load the Dump-capture
Kernel".)
2) Use a suitable value for "Physical address where the kernel is
loaded" (under "Processor type and features"). This only appears when
"kernel crash dumps" is enabled. By default this value is 0x1000000
(16MB). It should be the same as X in the "crashkernel=Y@X" boot
parameter.
For x86_64, normally "CONFIG_PHYSICAL_START=0x1000000".
3) Make and install the kernel and its modules. DO NOT add this kernel
to the boot loader configuration files.
Dump-capture kernel config options (Arch Dependent, ppc64) Dump-capture kernel config options (Arch Dependent, ppc64)
---------------------------------------------------------- ----------------------------------------------------------
...@@ -282,11 +261,9 @@ Based on the architecture and type of image (relocatable or not), one ...@@ -282,11 +261,9 @@ Based on the architecture and type of image (relocatable or not), one
can choose to load the uncompressed vmlinux or compressed bzImage/vmlinuz can choose to load the uncompressed vmlinux or compressed bzImage/vmlinuz
of dump-capture kernel. Following is the summary. of dump-capture kernel. Following is the summary.
For i386: For i386 and x86_64:
- Use vmlinux if kernel is not relocatable. - Use vmlinux if kernel is not relocatable.
- Use bzImage/vmlinuz if kernel is relocatable. - Use bzImage/vmlinuz if kernel is relocatable.
For x86_64:
- Use vmlinux
For ppc64: For ppc64:
- Use vmlinux - Use vmlinux
For ia64: For ia64:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment