From: Takao Indoh <indou.takao@jp.fujitsu.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, lkdump-develop@lists.sourceforge.net
Subject: Re: [lkdump-develop] Re: [ANNOUNCE 0/7] Diskdump 1.0 Release
Date: Mon, 29 Nov 2004 21:34:31 +0900 [thread overview]
Message-ID: <42C4D60FC636FDindou.takao@jp.fujitsu.com> (raw)
In-Reply-To: <1101727191.2814.52.camel@laptop.fenrus.org>
On Mon, 29 Nov 2004 12:19:52 +0100, Arjan van de Ven wrote:
>On Mon, 2004-11-29 at 19:35 +0900, Takao Indoh wrote:
>> Hi, all!
>> I release diskdump 1.0 for kernel 2.6.9. It can be downloaded from
>> the following site. Please feel free to use it!
>> http://sourceforge.net/projects/lkdump
>>
>> Diskdump project is a joint development of RedHat and Fujitsu, and I'd
>
>I think the company name is spelled Red Hat ;)
Sorry.
>> like to express my gratitude to a RedHat developers for many comments
>> and advices.
>
>Can you explain to me why anyone would want to use this invasive patch
>(it requires all drivers to change) instead of the kexec-dump approach? The
>kexec-dump approach appears on first sight to be far cleaner and far more
>powerful,
>so there must be a reason this work was done regardless of that.. I'm
>curious
>what those reasons are, eg what's the advantage ???
The problem of kexec-dump is that initialization of devices depends
on the quality of device driver when kexec reboots system. Sometimes the
device drivers tacitly rely on the firmware to initialize them.
Anyway, most important point is that kexec-dump is not available enough
now. I think kexec-dump is not stable yet. I heard that kexec-dump of
some architecture (ex. ia64) had some problems and not worked.
Best Regards,
Takao Indoh
next prev parent reply other threads:[~2004-11-29 12:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:35 [ANNOUNCE 0/7] Diskdump 1.0 Release Takao Indoh
2004-11-29 10:37 ` [ANNOUNCE 1/7] " Takao Indoh
2004-11-30 3:23 ` Rusty Russell
2004-12-01 0:50 ` Takao Indoh
2004-11-29 10:39 ` [ANNOUNCE 2/7] " Takao Indoh
2004-11-29 10:41 ` [ANNOUNCE 3/7] " Takao Indoh
2004-11-30 3:24 ` Rusty Russell
2004-11-29 10:43 ` [ANNOUNCE 4/7] " Takao Indoh
2004-11-29 10:45 ` [ANNOUNCE 5/7] " Takao Indoh
2004-11-29 10:47 ` [ANNOUNCE 6/7] " Takao Indoh
2004-11-29 10:48 ` [ANNOUNCE 7/7] " Takao Indoh
2004-11-29 11:19 ` [ANNOUNCE 0/7] " Arjan van de Ven
2004-11-29 12:34 ` Takao Indoh [this message]
2004-11-29 12:45 ` [lkdump-develop] " Arjan van de Ven
2004-11-30 1:15 ` Takao Indoh
2004-11-30 12:35 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2004-11-30 0:31 Itsuro Oda
2004-11-30 10:26 ` Vivek Goyal
2004-12-01 5:57 ` Itsuro Oda
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=42C4D60FC636FDindou.takao@jp.fujitsu.com \
--to=indou.takao@jp.fujitsu.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkdump-develop@lists.sourceforge.net \
/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