Re: [Fastboot] Yet another crash dump tool

[Itsuro Oda <oda@valinux.co.jp>]

Hi,

On 23 Dec 2004 04:59:03 -0700
ebiederm@xmission.com (Eric W. Biederman) wrote:

> developed right now.  Would you be willing to work on the kexec system
> call so we can get a infrastructure that reliably does what is needed
> for everyone? 

We concentrate on the fault analysis. We think the original aim of the
kexec (== fastboot) differ from the caputuring dump. However,
since we apply the effort of the kexec project to mkdump, we are happy
to return something to the kexec project. 

> Reading your documentation it seems to indicate that you have
> successfully avoid using any memory that the crashing kernel used.
> Is that correct?

No. If the code or the data structures running from crash occur to the
mini kernel start (although it is very short) is damaged, starting the 
mini kernel will fail.
What we done (and will do partialy) is that the logical possibility of 
the deadlock/hang condition is eliminated from the code running from 
crash occur to the mini kernel start.

> And just for a little active feedback.  While you safely tuck
> your kernel away in your reserved area of memory it does not appear
> you tuck away the data structures necessary to get there.  Which
> makes me just a little nervous.

What do you mean "the data structures necessary to get there" ?
The necessary information to run the mini kernel and to caputure dump 
is stored in the reserved area at the same time of loading the mini kernel
(during the kernel is normal).

> Eric

Thanks.
-- 
Itsuro ODA <oda@valinux.co.jp>