From: "Michael Frank" <mhf@linuxmail.org>
To: "Pavel Machek" <pavel@suse.cz>
Cc: "Andrea Arcangeli" <andrea@suse.de>,
"Nigel Cunningham" <ncunningham@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: Reserved page flaging of 2.4 kernel memory changed recently?
Date: Thu, 19 Feb 2004 17:00:05 +0800 [thread overview]
Message-ID: <opr3l0mfdw4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <20040219072629.GB467@openzaurus.ucw.cz>
On Thu, 19 Feb 2004 08:26:30 +0100, Pavel Machek <pavel@suse.cz> wrote:
> Hi!
>
mhf wrote:
>> I actually would like to rename the bit PG_nosave to PG_donttouch ;)
to make a point with regard to:
no transfer of page contents during suspend/resume
no netdump
no debugger access without override
... but the name does not matter and we do not have to change it.
>
> Its used for swsusp internal data, too...
Yes of course - how else would swsusp run, but these data are also not
"touched"
during suspend and resume wrt transfer of page content.
x86 Pages for PG_nosave:
Video/BIOS 0xA0000-0XFFFFF
Anything reserved < max_pfn
Pentium 2 broken highmem pages
Driver specific areas in DMA zone are also thinkable
.. or else you get mce's or possibly crashes on newer x86 HW and on 64Bit
for sure.
- we had a mce recently at 0xa0000 on a Athlon XP and I went digging...
Regards
Michael
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
next prev parent reply other threads:[~2004-02-19 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 2:07 Michael Frank
2004-02-08 2:06 ` Andrea Arcangeli
2004-02-10 15:24 ` Michael Frank
2004-02-10 18:51 ` Andrea Arcangeli
2004-02-10 19:38 ` Michael Frank
2004-02-11 8:36 ` Michael Frank
2004-02-19 7:26 ` Pavel Machek
2004-02-19 9:00 ` Michael Frank [this message]
2004-02-19 16:14 ` Pavel Machek
2004-02-19 17:37 ` Michael Frank
2004-02-19 17:35 ` Pavel Machek
2004-02-19 17:59 ` Michael Frank
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=opr3l0mfdw4evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®