Re: [KEXEC][PATCH] Modified (smaller) x86 kexec hwfixes patch

From: Eric W. Biederman (
Date: Fri Feb 14 2003 - 11:00:16 EST

"Martin J. Bligh" <> writes:

> >> Running on my 4-way P3 test box (just SMP, not NUMA) kexec_test
> >> prints this:
> >>
> >> Synchronizing SCSI caches:
> >> Shutting down devices
> >> Starting new kernel
> >> kexec_test 1.8 starting...
> >> eax: 0E1FB007 ebx: 0000011C ecx: 00000000 edx: 00000000
> >> esi: 00000000 edi: 00000000 esp: 00000000 ebp: 00000000
> >> idt: 00000000 C0000000
> >> gdt: 0000006F 000000A0
> >> Switching descriptors.
> >> Descriptors changed.
> >> Legacy pic setup.
> >> In real mode.
> >>
> >> Without that I just get:
> >>
> >> Synchronizing SCSI caches:
> >> Shutting down devices
> >> Starting new kernel
> >>
> >> Can someone interpret?
> >
> > Besides the fact that you cannot make BIOS calls, and kexec is working
> > there is not much to say. You cannot kexec another kernel?
> Nope, if I just kexec the same 2.5.59 kernel+kexec patches that I'm booted
> on it says:
> Synchronizing SCSI caches:
> Shutting down devices
> Starting new kernel
> Could you give me a high-level sketch of what you're doing? kexec -l loads
> the new kernel, then what do you do? Drop back into real mode and jump to
> the normal kernel entry point? Or decompress by hand, do some alternate
> setup of the early page tables and try to jump in at the 32-bit entry point?

With Interrupts disabled.
machine_kexec switch the cpu to physical address mode (it turns the mmu off).
Copies the kernel to where it needs to run.
Then it jumps to an entry point.

kexec has put in a stub piece of code, and pointed the entry point at that location.
The stub code setups of a gdt, the kernel can cope with.
The stub code setups a parameter table just like the real mode code generates.
The stub code jumps in at the 32bit entry point.

[There is another stub that will attempt to start the kernel at the 16bit entry
 point but it is not used by default].

Interrupts are off the entire time.

> Is all I can assume from the above that I crash in the new kernel before
> console_init()?


> Or should I expect something from the decompress code?

It is not hard to patch the decompression code to display a message, but
by default it does not output to serial...

You might want to run mkelfImage on a vmlinux so you can skip the decompression
step. It adds a stub to the elf file that gets passed to kexec so that
you can skip the decompression.

Also I have some assembly language macros that display text out the serial port, if you want
to instrument up the kernel you are booting.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:55 EST