Bootloaders with early kdump support?

Bootloaders with early kdump support?

[Nathan D Miller]

[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]


Greetings-

Vivek made the following statement a few months ago:

> On a side note, few months back there were folks who were trying
> to enhance bootloaders to be able to prepare basic environment so
> that a kdump kernel can boot even in the event of early first
> kernel boot.

Any idea which bootloaders?  Which folks?

I'm curious how one would go about implementing such a thing.  What
parameters would the bootloader need to supply to the kernel?

Thanks,
Nate

[-- Attachment #1.2: Type: text/html, Size: 849 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

Re: Bootloaders with early kdump support?

[Lei Wen]

Hi Nathan,

On Fri, Aug 19, 2011 at 6:21 AM, Nathan D Miller <nathanm2@us.ibm.com> wrote:
> Greetings-
>
> Vivek made the following statement a few months ago:
>
>> On a side note, few months back there were folks who were trying
>> to enhance bootloaders to be able to prepare basic environment so
>> that a kdump kernel can boot even in the event of early first
>> kernel boot.
>
> Any idea which bootloaders?  Which folks?
>
> I'm curious how one would go about implementing such a thing.  What
> parameters would the bootloader need to supply to the kernel?

Actually I ask a similar question for it, but sightly different at
that I try to trigger
the dump kernel at the moment the first kernel unable to trigger. Core hang, or
very bad dead lock all could lead to this...

I recently make some patches to both the kernel and kexec tools side, and basic
idea is:
1) Move copy kernel relocation code to the stage of
machine_kexec_prepare() from original
in machine_kexec()
2) Provide a new supported flags for kexec_load api to support
crash_update method. In this
method,  I would call crash_setup_regs(), crash_save_vmcoreinfo() and
machine_crash_update().
3) Add patch to kexec to support the new supported flags. This new
made method could be called
as a daemon in the kernel, and the info pass to the crash kernel could
be gotten updated to
the point of dead lock.
4) After kernel meet core hang, we reset the board and while enter the
uboot, we let the uboot to
directly transfer the control to the crash kernel. Since crash kernel
is already loaded, and reloaction
code and parameter all has been set up. There is no more effort for
the bootloader, just transferring
control would do the all good.

Best regards,
Lei

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec