[lkml]   [2004]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [lkdump-develop] Re: [ANNOUNCE 0/7] Diskdump 1.0 Release

I am a developer of an yet another crash dump (mkdump).
I'd like to know conditions which cause taking dump fail.
It is helpful to share those informations for dump developers.

I have three major concerns about taking dump.
* interrupt disable
taking dump should be run under interrput disable.
diskdump is aware of that. How about kexec based dump ?
* avoid deadlock
taking dump should not get any locks to avoid deadlock. (?)
I think there are many posibility of deadlock in the kexec
based dump (from crash occur to initiate the new kernel).
(mkdump does not meet neither yet. :-p)
* be sure to get the other CPUs' register value
How are the other CPUs' regsiter value get and how are the
other CPUs stoped ?
(of course the goal of mkdump is to solve these points
although not implemented yet :-)

Any other points to be consider ?
Comments and suggestions are welcome.

Thank you.
Itsuro ODA <>

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

 \ /
  Last update: 2005-03-22 14:08    [W:0.075 / U:1.152 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site