From: Josh Huber <huberj@wpi.edu>
To: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Preserving memory...
Date: Tue, 11 Apr 2000 15:19:58 -0400 [thread overview]
Message-ID: <20000411151958.H771@mclinux.com> (raw)
Hey, I'm working to get some in-memory crash dump kernel patches, and I've
run into some problems. I've got a couple of questions that I hope someone
can answer for me:
First, is there a way to tell powerpc hardware (Macs in particular -- for
now) to preserve memory across a system restart? It looks like it does this
by default, partially.
Secondly, if I can get the first part to work reliably, does anyone know
what regions of memory should be avoided, i.e. are thrashed by OF etc?
Thanks,
Josh
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-11 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 19:19 Josh Huber [this message]
2000-04-15 13:28 ` Preserving memory Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2000-04-15 16:40 Iain Sandoe
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=20000411151958.H771@mclinux.com \
--to=huberj@wpi.edu \
--cc=linuxppc-dev@lists.linuxppc.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).