public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Vidal <bruno_vidal@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Dump driver module
Date: Tue, 13 May 2003 07:02:48 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705751@msgid-missing> (raw)

	Hi all.
I've already wrote a dump modules driver for linux-parisc.
This module goal is to create a memory image on a swap area, and
at reboot time to save it to disk with all kernel modules, in
order to analyze it after by "support" people with tools like
gdb/p4. The problem while dumping is that the dump modules
cannot trust anymore the system, so dumping means: no interruption,
no disk driver, no buffer, nothing. The solution is to use low level
call. For parisc I use the IODC calls, for ia64 I think I'll
use the EFI calls. My questions:
-do you think it is a "good" and realistic solution.
-because I think "yes", does exist somewhere an example of
reading/writing with EFI call on disk using BLOCK IO. I've already
looked in elilo, but it seems that it use FS access.

	Thanks.

-- 
	Vidal Bruno, (770-4271)
         SSD-HA Team, HP-UX & LINUX Support
	bruno_vidal@admin.france.hp.com



             reply	other threads:[~2003-05-13  7:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  7:02 Bruno Vidal [this message]
2003-05-13  7:18 ` [Linux-ia64] Dump driver module Stephane Eranian
2003-05-13  7:25 ` David Mosberger
2003-05-13  7:38 ` Bruno Vidal
2003-05-13  8:08 ` David Mosberger
2003-05-13 13:29 ` Howell, David P
2003-05-13 14:39 ` Bruno Vidal
2003-05-14  2:13 ` Keith Owens
2003-05-14  2:14 ` Martin Pool
2003-05-14  2:21 ` David Mosberger
2003-05-14  2:32 ` Martin Pool
2003-05-14  2:40 ` David Mosberger
2003-05-14  6:33 ` Grant Grundler
2003-05-14  6:50 ` Bruno Vidal
2003-05-14 13:29 ` Matthew Wilcox
2003-05-14 15:41 ` Grant Grundler

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=marc-linux-ia64-105590723705751@msgid-missing \
    --to=bruno_vidal@hp.com \
    --cc=linux-ia64@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