LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Takao Indoh <indou.takao@soft.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]Diskdump - yet another crash dump function
Date: Fri, 4 Jun 2004 11:33:44 +0200	[thread overview]
Message-ID: <20040604093344.GA700@elf.ucw.cz> (raw)
In-Reply-To: <4BC449CD20D638indou.takao@soft.fujitsu.com>

Hi!

> >> Although I know about LKCD and netdump, I'm developing yet another crash
> >> dump, which is a polling-based disk dump as netdump do. Because it
> >> disables any interrupts during doing dump, it can avoid lots of problems
> >> LKCD has.
> >> 
> >> Main Feature
> >> - Reliability
> >>    Diskdump disables interrupts, stops other cpus and writes to the 
> >>    disk with polling mode. Therefore, unnecessary functions(like
> >>    interrupt handler) don't disturb dumping.
> >
> >Hmm... with this, better design of swsusp mifht be feasible.
> 
> I don't know mechanism of swsusp well.
> Do you mean diskdump is useful when saving system memory to the disk?

Yes. Self-contained code accessing disk would be usefull both when
saving system memory and when reading it back. (This is probably 2.8
material, through).
							Pavel

-- 
934a471f20d6580d5aad759bf0d97ddc

  reply	other threads:[~2004-06-04  9:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27  9:33 [PATCH]Diskdump - yet another crash dump function Takao Indoh
2004-05-27 12:36 ` [1/4] " Takao Indoh
2004-05-27 12:37 ` [2/4] " Takao Indoh
2004-05-27 13:48   ` Christoph Hellwig
2004-05-28  2:13     ` Takao Indoh
2004-05-27 12:39 ` [3/4] " Takao Indoh
2004-05-27 13:51   ` Christoph Hellwig
2004-05-27 21:04     ` Ingo Molnar
2004-06-17 11:34       ` Takao Indoh
2004-06-17 12:00         ` Christoph Hellwig
2004-06-17 12:45           ` Takao Indoh
2004-06-17 12:13         ` Ingo Molnar
2004-06-17 12:18           ` Christoph Hellwig
2004-06-17 12:32             ` Ingo Molnar
2004-06-17 14:56               ` Jeff Moyer
2004-06-17 15:45                 ` Nobuhiro Tachino
2004-06-17 13:04           ` Takao Indoh
2004-06-17 13:10             ` Ingo Molnar
2004-06-17 13:11               ` Ingo Molnar
2004-06-17 13:15                 ` Ingo Molnar
2004-06-17 14:00                 ` Takao Indoh
2004-06-17 14:45                   ` Nobuhiro Tachino
2004-06-17 14:53                     ` Takao Indoh
2004-06-18 12:02           ` Takao Indoh
2004-06-21 20:40             ` Nobuhiro Tachino
2004-06-22 10:19               ` Ingo Molnar
2004-06-23 12:11                 ` Takao Indoh
2004-06-23 13:00                   ` Takao Indoh
2004-06-21  5:46           ` Keith Owens
2004-06-21  6:25             ` Takao Indoh
2004-06-22  4:21             ` Rob Landley
2004-06-22  7:56             ` Ingo Molnar
2004-05-28  9:38     ` Takao Indoh
2004-05-27 12:40 ` [4/4] " Takao Indoh
2004-05-27 13:34 ` [Document][PATCH]Diskdump " Takao Indoh
2004-06-03 13:10 ` [PATCH]Diskdump " Pavel Machek
2004-06-04  0:44   ` Takao Indoh
2004-06-04  9:33     ` Pavel Machek [this message]
     [not found] <20pwP-55v-5@gated-at.bofh.it>
2004-05-27 13:19 ` Andi Kleen
2004-05-27 13:49   ` Christoph Hellwig
2004-05-27 14:02   ` Takao Indoh
2004-05-27 14:45   ` Nobuhiro Tachino

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=20040604093344.GA700@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=indou.takao@soft.fujitsu.com \
    --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;
as well as URLs for NNTP newsgroup(s).