From: Itsuro Oda <oda@valinux.co.jp>
To: linux-kernel@vger.kernel.org
Subject: Re: [lkdump-develop] Re: [ANNOUNCE 0/7] Diskdump 1.0 Release
Date: Tue, 30 Nov 2004 09:31:03 +0900 [thread overview]
Message-ID: <20041130083116.3D92.ODA@valinux.co.jp> (raw)
Hi,
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 <oda@valinux.co.jp>
next reply other threads:[~2004-11-30 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 0:31 Itsuro Oda [this message]
2004-11-30 10:26 ` Vivek Goyal
2004-12-01 5:57 ` Itsuro Oda
-- strict thread matches above, loose matches on Subject: below --
2004-11-29 11:19 Arjan van de Ven
2004-11-29 12:34 ` [lkdump-develop] " Takao Indoh
2004-11-29 12:45 ` Arjan van de Ven
2004-11-30 1:15 ` Takao Indoh
2004-11-30 12:35 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041130083116.3D92.ODA@valinux.co.jp \
--to=oda@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®