From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andi Kleen <ak@suse.de>
Cc: "Discuss x86-64" <discuss@x86-64.org>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFC][PATCH][Fix] swsusp: Yet another attempt to fix Bug #4959
Date: Tue, 4 Oct 2005 16:11:28 +0200 [thread overview]
Message-ID: <200510041611.28763.rjw@sisk.pl> (raw)
In-Reply-To: 200510012145.30067.ak@suse.de
On Sunday, 2 of October 2005 12:06, Rafael J. Wysocki wrote:
> On Saturday, 1 of October 2005 21:45, Andi Kleen wrote:
> > On Saturday 01 October 2005 18:13, Rafael J. Wysocki wrote:
> >
> > >
> > > This function allocates twice as much memory as needed for the direct
> > > mapping page tables and assigns the second half of it to the resume page
> > > tables. This area is later marked with PG_nosave by swsusp, so that it is
> > > not overwritten during resume.
> > >
> > I prefered it when the additional page tables were allocated only on demand.
>
> Me too. Let's get back to that patch, then. :-)
>
> Comments etc. will be appreciated.
I haven't got any comments since I posted it on Saturday, so I gather there are
no objections. Or are there any?
Greetings,
Rafael
next prev parent reply other threads:[~2005-10-04 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 16:13 [RFC][PATCH][Fix] swsusp: Yet another attempt to fix Bug #4959 Rafael J. Wysocki
2005-10-01 19:45 ` Andi Kleen
2005-10-02 10:25 ` Rafael J. Wysocki
2005-10-04 14:11 ` Rafael J. Wysocki [this message]
2005-10-04 17:09 ` [discuss] " Andi Kleen
2005-10-04 21:31 ` Rafael J. Wysocki
2005-10-05 21:44 ` [PATCH][Fix] swsusp: avoid possible page tables corruption during resume on x86-64 Rafael J. Wysocki
2005-10-05 22:49 ` Pavel Machek
2005-10-06 8:07 ` [discuss] " Rafael J. Wysocki
2005-10-08 10:30 ` Andi Kleen
2005-10-08 12:23 ` 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=200510041611.28763.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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