From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH][Fix] Fix Bug #4959 (take 2)
Date: Wed, 28 Sep 2005 01:43:29 +0200 [thread overview]
Message-ID: <20050927234329.GC2381@elf.ucw.cz> (raw)
In-Reply-To: <200509280126.26701.rjw@sisk.pl>
Hi!
> > > I can reserve the static buffer (10 pages) in suspend.c and mark it as nosave.
> > > The code that creates the mappings can stay in suspend.c either except it
> > > won't need to call get_usable_page() and free_eaten_memory() any more
> > > (__next_page() can be changed to get pages from the static buffer instead
> > > of allocating them). The code can also be simplified a bit, as we assume that
> > > there will be only one PGD entry in the direct mapping.
> > >
> > > If that sounds good to you, please confirm.
> >
> > 8GB limit seems good to me -- as long as it makes code significantly
> > simpler. It would be nice if it was <20 lines.
>
> It is more than that, but it seems to be quite simple anyway.
>
> The new patch follows.
Thanks, seems okay to me.
Pavel
--
if you have sharp zaurus hardware you don't need... you know my address
next prev parent reply other threads:[~2005-09-27 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 17:36 [PATCH][Fix] Prevent swsusp from corrupting page translation tables during resume on x86-64 Rafael J. Wysocki
2005-09-25 22:07 ` Pavel Machek
2005-09-26 10:46 ` Rafael J. Wysocki
2005-09-26 10:49 ` Pavel Machek
2005-09-27 8:07 ` [PATCH][Fix] Fix Bug #4959 (take 2) Rafael J. Wysocki
2005-09-27 13:32 ` Pavel Machek
2005-09-27 21:00 ` Rafael J. Wysocki
2005-09-27 21:08 ` Pavel Machek
2005-09-27 23:26 ` Rafael J. Wysocki
2005-09-27 23:43 ` Pavel Machek [this message]
2005-09-28 8:25 ` Rafael J. Wysocki
2005-09-28 10:29 ` [PATCH][Fix] Fix Bug #4959 (take 3) 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=20050927234329.GC2381@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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