From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Dump driver module
Date: Tue, 13 May 2003 07:25:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705753@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705751@msgid-missing>
>>>>> On Tue, 13 May 2003 09:02:48 +0200, Bruno Vidal <bruno_vidal@hp.com> said:
Bruno> I've already wrote a dump modules driver for linux-parisc.
Bruno> This module goal is to create a memory image on a swap area, and
Bruno> at reboot time to save it to disk with all kernel modules, in
Bruno> order to analyze it after by "support" people with tools like
Bruno> gdb/p4. The problem while dumping is that the dump modules
Bruno> cannot trust anymore the system, so dumping means: no interruption,
Bruno> no disk driver, no buffer, nothing. The solution is to use low level
Bruno> call. For parisc I use the IODC calls, for ia64 I think I'll
Bruno> use the EFI calls. My questions:
Bruno> -do you think it is a "good" and realistic solution.
Bruno> -because I think "yes", does exist somewhere an example of
Bruno> reading/writing with EFI call on disk using BLOCK IO. I've already
Bruno> looked in elilo, but it seems that it use FS access.
Once the kernel is booted, you can access only the EFI runtime
services (see struct efi in include/linux/efi.h). I'm afraid there is
no support for writing disk blocks. Given this limitation, I suspect
you'd have to include your own (simple) disk driver(s).
--david
next prev parent reply other threads:[~2003-05-13 7:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 7:02 [Linux-ia64] Dump driver module Bruno Vidal
2003-05-13 7:18 ` Stephane Eranian
2003-05-13 7:25 ` David Mosberger [this message]
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-105590723705753@msgid-missing \
--to=davidm@napali.hpl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.