Dave Hansen <haveblue@us.ibm.com> writes:
> Eric W. Biederman wrote:
> > kexec is a set of systems call that allows you to load another kernel
> > from the currently executing Linux kernel. The current implementation
> > has only been tested, and had the kinks worked out on x86, but the
> > generic code should work on any architecture.
> > Could I get some feed back on where this work and where this breaks.
> > With the maturation of kexec-tools to skip attempting bios calls,
> > I expect a new the linux kernel to load for most people. Though I
> > also expect some device drivers will not reinitialize after the reboot.
>
> I give it a big thumbs-up.
And you thought I was kidding when I said it was mostly working :)
> Between the NUMAQs and the big xSeries machines, we
> have a lot of slow rebooters. The 16GB intel boxes take at about 5 minutes to
> get back to the bootloader after a reboot, and the 4 and 8-quad NUMAQ's take
> closer to 10.
Wow. 10 minutes is a pain. That certainly explains your interest...
> The IBM machines I've tried it on are a 4-way and 8-way PIII. They both have
> aic7xxx cards and the 8-way has a ServeRAID 4 controller. They have a collection
>
> of acenic, e1000, pcnet32 and eepro100 net cards. All seem to work just fine.
>
> The NUMAQ is another story, though. I get nothing after "Starting new kernel".
> But, I wasn't expecting much. The NUMAQ is pretty weird hardware and god knows
> what is actually happening. I'll try it some more when I'm more confident in
> what I'm doing.
I suspect the hardware shutdown and start up logic for NUMAQ cpus needs some
special handling. Does kexec_test not print anything, or were you not patient
enough?
> What's the deal with "FIXME assuming 64M of ram"? I was a little surprised when
>
> my 16GB machine started to OOM as I did a "make -j8 bzImage" :) Why is it that
> you need the memory size at load time?
Small steps. When I bypass the BIOS I need to get all of the information
the kernel normally would get from the BIOS from someplace else. Currently
you can use the "mem= " kernel command line parameters. Of you can dig the
/proc/iomem and /proc/meminfo and other places and get the BIOS's memory map.
There isn't a really good source, so I started with something that would work,
and I will work the user space tools up to something that works well.
I will happily accept patches :)
Eric
-
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/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:27 EST