On Fri, Jan 12, 2007 at 11:46:39AM -0800, Jay Lan wrote:
> Horms wrote:
> > 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.
> >
> > Take II
> >
> > Nanhai,
> >
> > I have noted that vmlinux.gz may also be used. And added a note about the
> > kernel being able to automatically place the crashkernel region.
> > Furthermore, I added a note that if manually specified, the region should
> > be 64Mb aligned to avoid wastage. I notice that the auto placement code
> > uses 64Mb. But is this strictly neccessary for all page sizes?
> >
> > Signed-off-by: Simon Horman <[email protected]>
> >
> > Index: linux-2.6/Documentation/kdump/kdump.txt
> > ===================================================================
> > --- linux-2.6.orig/Documentation/kdump/kdump.txt 2007-01-12 17:45:19.000000000 +0900
> > +++ linux-2.6/Documentation/kdump/kdump.txt 2007-01-12 17:59:42.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
> > @@ -229,7 +229,23 @@
> >
> > 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.
>
> In my testing, i found the base address was ignored. Whatever value
> specified was fine. Not necessary to be 0. But i guess it is fine to
> give people a guideline telling them to specify 0.
I submitted a patch to honour non-zero base addresses,
I'm pretty sure it is in there now.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
