From: Michael Frank <mhf@linuxmail.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Nigel Cunningham <ncunningham@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: Reserved page flaging of 2.4 kernel memory changed recently?
Date: Wed, 11 Feb 2004 03:38:10 +0800 [thread overview]
Message-ID: <200402110338.10258.mhf@linuxmail.org> (raw)
In-Reply-To: <20040210185137.GD4478@dualathlon.random>
On Wednesday 11 February 2004 02:51, Andrea Arcangeli wrote:
> On Tue, Feb 10, 2004 at 11:24:01PM +0800, Michael Frank wrote:
> >
> > diff -uN -r -X /home/mhf/sys/dont/dontdiff linux-2.4.24-Vanilla/arch/i386/mm/init.c linux-2.4.24-mhf179/arch/i386/mm/init.c
> > --- linux-2.4.24-Vanilla/arch/i386/mm/init.c 2004-01-21 15:53:01.000000000 +0800
> > +++ linux-2.4.24-mhf179/arch/i386/mm/init.c 2004-02-10 06:15:31.000000000 +0800
> > @@ -451,15 +451,18 @@
> > {
> > if (!page_is_ram(pfn)) {
> > SetPageReserved(page);
> > + SetPageNosave(page);
> > return;
> > }
> >
> > if (bad_ppro && page_kills_ppro(pfn)) {
> > SetPageReserved(page);
> > + SetPageNosave(page);
> > return;
> > }
> >
> > ClearPageReserved(page);
> > + ClearPageNosave(page);
>
> why this clearpagenosave? looks superflous, you're not doing it in the
> normal zone anyways.
I'll sleep on it and get back to you with my arguments.
>
> > +#if defined(__nosave_begin)
>
> this won't work right, __nosave_begin isn't a preprocessor thing so it
> will be ignored when you uncomment it. You probably can use #if 0
> instead and a comment near __nosave_begin to turn it to 1 when enabling
> the suspend code.
Oh sh*t, this is what one gets for fixing things up for a demo after
a long night... Will bite my lower rear portion after the nap.
>
> > What is your opinion of this approach?
>
> except for the above two nitpicks, the patch is correct and needed for
> safe suspend IMHO. 2.6 seems to miss this thing too, why not add it to
> 2.6 first?
Swsusp won't be in 2.4 anyway, if Nigel accepts the patch, it will become part
of his next releases for 2.4 and 2.6.
Anyway, I'll fix the patch up for 2.6, test it and post the patch in a few days.
Regards
Michael
next prev parent reply other threads:[~2004-02-10 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 2:07 Reserved page flaging of 2.4 kernel memory changed recently? 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 [this message]
2004-02-11 8:36 ` Michael Frank
2004-02-19 7:26 ` Pavel Machek
2004-02-19 9:00 ` Michael Frank
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=200402110338.10258.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
/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