Messages in this thread | | | Subject | RE: [PATCH] Kdump documentation update for 2.6.20: ia64 portion | Date | Fri, 12 Jan 2007 16:34:32 +0800 | From | "Zou, Nanhai" <> |
| |
> -----Original Message----- > From: linux-ia64-owner@vger.kernel.org > [mailto:linux-ia64-owner@vger.kernel.org] On Behalf Of Horms > Sent: 2007年1月12日 14:07 > To: Vivek Goyal > Cc: Mohan Kumar M; Andrew Morton; Zou, Nanhai; Luck, Tony; > linux-kernel@vger.kernel.org; fastboot@lists.osdl.org; > linux-ia64@vger.kernel.org > Subject: [PATCH] Kdump documentation update for 2.6.20: ia64 portion > > Hi, > > this patch fills in the portions for ia64 kexec. > > I'm actually not sure what options are required for the dump-capture > kernel, but "init 1 irqpoll maxcpus=1" has been working fine for me. > Or more to the point, I'm not sure if irqpoll is needed or not. > > This patch requires the documentation patch update that Vivek Goyal has > been circulating, and I believe is currently in mm. Feel free to fold it > into that change if it makes things easier for anyone. > > Signed-off-by: Simon Horman <horms@verge.net.au> > > Index: linux-2.6/Documentation/kdump/kdump.txt > =================================================================== > --- linux-2.6.orig/Documentation/kdump/kdump.txt 2007-01-12 > 14:37:46.000000000 +0900 > +++ linux-2.6/Documentation/kdump/kdump.txt 2007-01-12 > 14:46:53.000000000 +0900 > @@ -17,7 +17,7 @@ > 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 > @@ -227,7 +227,11 @@ > > 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. > > > Boot into System Kernel > @@ -264,7 +268,8 @@ > For ppc64: > - Use vmlinux > For ia64: > - (To be filled) > + - Use vmlinux > + You can also use gziped vmlinux.gz here. > > If you are using a uncompressed vmlinux image then use following command > to load dump-capture kernel. > @@ -280,18 +285,19 @@ > --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: > We can add note about that IA64 can automatically pick crash dump region according to size to reserve.
Thanks Zou Nan hai - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |