From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Dump driver module
Date: Wed, 14 May 2003 02:40:50 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705773@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705751@msgid-missing>
>>>>> On Wed, 14 May 2003 12:32:17 +1000, Martin Pool <mbp@samba.org> said:
Martin> So for a really reliable dump, you'd want to check and "lock
Martin> down" these variables at startup into a region of memory not
Martin> easily changed by the kernel, and accessible by EFI. NVRAM?
Martin> I don't know if there's anything suitable on IPF.
EFI provides (persistent) environment variables for this purpose.
Don't know how well they're protected, typically, but that's probably
more of an implementation issue than anything else.
Martin> It would be an interesting project, although since network
Martin> dumps run a lower risk of clobbering filesystems they're
Martin> probably a smarter design. It would be cool to do it in
Martin> EFI, if that's possible.
"Smart" is relative. I'm typing this on an Itanium box which doesn't
have anything on the network that could serve as a dump device (it's
own disk would be fine, though).
--david
next prev parent reply other threads:[~2003-05-14 2:40 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
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 [this message]
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-105590723705773@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox