[PATCH] Kdump documentation update: ia64 portion

this patch fills in the portions for ia64 kexec.

Signed-off-by: Simon Horman <horms@verge.net.au>
Cc: "Zou, Nanhai" <nanhai.zou@intel.com>
Cc: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

authored by Horms and committed by Linus Torvalds ee8bb9ea ea112bd5

+29 -7
+29 -7
Documentation/kdump/kdump.txt
··· 17 17 memory image to a dump file on the local disk, or across the network to 18 18 a remote system. 19 19 20 - Kdump and kexec are currently supported on the x86, x86_64, ppc64 and IA64 20 + Kdump and kexec are currently supported on the x86, x86_64, ppc64 and ia64 21 21 architectures. 22 22 23 23 When the system kernel boots, it reserves a small section of memory for ··· 229 229 230 230 Dump-capture kernel config options (Arch Dependent, ia64) 231 231 ---------------------------------------------------------- 232 - (To be filled) 232 + 233 + - No specific options are required to create a dump-capture kernel 234 + for ia64, other than those specified in the arch idependent section 235 + above. This means that it is possible to use the system kernel 236 + as a dump-capture kernel if desired. 237 + 238 + The crashkernel region can be automatically placed by the system 239 + kernel at run time. This is done by specifying the base address as 0, 240 + or omitting it all together. 241 + 242 + crashkernel=256M@0 243 + or 244 + crashkernel=256M 245 + 246 + If the start address is specified, note that the start address of the 247 + kernel will be aligned to 64Mb, so if the start address is not then 248 + any space below the alignment point will be wasted. 233 249 234 250 235 251 Boot into System Kernel ··· 263 247 On x86 and x86_64, use "crashkernel=64M@16M". 264 248 265 249 On ppc64, use "crashkernel=128M@32M". 250 + 251 + On ia64, 256M@256M is a generous value that typically works. 252 + The region may be automatically placed on ia64, see the 253 + dump-capture kernel config option notes above. 266 254 267 255 Load the Dump-capture Kernel 268 256 ============================ ··· 286 266 For ppc64: 287 267 - Use vmlinux 288 268 For ia64: 289 - (To be filled) 269 + - Use vmlinux or vmlinuz.gz 270 + 290 271 291 272 If you are using a uncompressed vmlinux image then use following command 292 273 to load dump-capture kernel. ··· 303 282 --initrd=<initrd-for-dump-capture-kernel> \ 304 283 --append="root=<root-dev> <arch-specific-options>" 305 284 285 + Please note, that --args-linux does not need to be specified for ia64. 286 + It is planned to make this a no-op on that architecture, but for now 287 + it should be omitted 288 + 306 289 Following are the arch specific command line options to be used while 307 290 loading dump-capture kernel. 308 291 309 - For i386 and x86_64: 292 + For i386, x86_64 and ia64: 310 293 "init 1 irqpoll maxcpus=1" 311 294 312 295 For ppc64: 313 296 "init 1 maxcpus=1 noirqdistrib" 314 - 315 - For IA64 316 - (To be filled) 317 297 318 298 319 299 Notes on loading the dump-capture kernel: