From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andi Kleen <ak@suse.de>,
kernel list <linux-kernel@vger.kernel.org>,
paul.devriendt@amd.com,
Nigel Cunningham <ncunningham@cyclades.com>
Subject: Re: BIOS overwritten during resume (was: Re: Asus L5D resume on battery power)
Date: Sun, 6 Mar 2005 20:41:00 +0100 [thread overview]
Message-ID: <20050306194100.GA1528@elf.ucw.cz> (raw)
In-Reply-To: <200503061830.00574.rjw@sisk.pl>
Hi!
> > > Yes. I thought about using PG_nosave in the begining, but there's a
> > >
> > > BUG_ON(PageReserved(page) && PageNosave(page));
> > >
> > > in swsusp.c:saveable() that I just didn't want to trigger. It seems to me,
> > > though, that we don't need it any more, do we?
> >
> > No, we can just kill it. It was "if something unexpected happens, bail
> > out soon".
>
> OK
>
> The following is what I'm comfortable with. I didn't took the Nigel's patch
> literally, because we do one thing differently (ie nosave pfns) and it contained
> some changes that I thought were unnecessary. The i386 part is
> untested.
I'd add
> page = pfn_to_page(pfn);
> - BUG_ON(PageReserved(page) && PageNosave(page));
a comment here explaining what PageReserved && PageNosave means.
> if (PageNosave(page))
> return 0;
> +
> if (PageReserved(page) && pfn_is_nosave(pfn)) {
> pr_debug("[nosave pfn 0x%lx]", pfn);
> return 0;
AFAICT it only fixes "potential" bug, so it can probably wait. Once
non-contiguous and initramfs patches are in, this can go...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-03-06 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200502252237.04110.rjw@sisk.pl>
[not found] ` <20050227170253.GH1441@elf.ucw.cz>
[not found] ` <200502271919.45767.rjw@sisk.pl>
[not found] ` <200503022250.12823.rjw@sisk.pl>
2005-03-02 22:05 ` BIOS overwritten during resume (was: Re: Asus L5D resume on battery power) Pavel Machek
2005-03-02 23:47 ` Rafael J. Wysocki
2005-03-02 23:54 ` Pavel Machek
2005-03-03 8:02 ` Rafael J. Wysocki
2005-03-04 11:04 ` Pavel Machek
2005-03-04 13:15 ` Rafael J. Wysocki
2005-03-04 14:44 ` Nigel Cunningham
2005-03-04 20:11 ` Pavel Machek
2005-03-04 23:26 ` Rafael J. Wysocki
2005-03-04 23:37 ` Nigel Cunningham
2005-03-05 0:51 ` Bernard Blackham
2005-03-04 23:41 ` Pavel Machek
2005-03-05 1:10 ` Nigel Cunningham
2005-03-05 9:08 ` Rafael J. Wysocki
2005-03-06 17:29 ` Rafael J. Wysocki
2005-03-06 19:41 ` Pavel Machek [this message]
2005-03-06 21:53 ` Rafael J. Wysocki
2005-03-04 14:21 ` Nigel Cunningham
2005-03-05 18:43 ` Rafael J. Wysocki
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=20050306194100.GA1528@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=paul.devriendt@amd.com \
--cc=rjw@sisk.pl \
/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