From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>, Jiri Slaby <jslaby@suse.cz>,
Len Brown <lenb@kernel.org>
Subject: Re: [patch 1/1] [PATCH] include storage keys in hibernation image.
Date: Thu, 7 Jul 2011 23:36:25 +0200 [thread overview]
Message-ID: <201107072336.26151.rjw@sisk.pl> (raw)
In-Reply-To: <20110615093629.07f01779@mschwide>
On Wednesday, June 15, 2011, Martin Schwidefsky wrote:
> On Tue, 14 Jun 2011 22:50:14 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
...
>
> Well before the preallocation kicked in we don't know which are the relevant
> storage keys. The only other option would be to store all of them which I
> consider to be a inferior solution.
I've been thinking about that recently a bit.
Don't we need to restore the keys of the page frames that aren't copied
into the image too?
Rafael
next prev parent reply other threads:[~2011-07-07 21:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 7:45 [patch 0/1] [RFC] include storage keys in hibernation image Martin Schwidefsky
2011-06-08 7:45 ` [patch 1/1] [PATCH] " Martin Schwidefsky
2011-06-12 12:41 ` Rafael J. Wysocki
2011-06-14 8:50 ` Martin Schwidefsky
2011-06-14 20:50 ` Rafael J. Wysocki
2011-06-15 7:36 ` Martin Schwidefsky
2011-06-15 23:21 ` Rafael J. Wysocki
2011-07-03 17:46 ` Pavel Machek
2011-07-04 8:09 ` Martin Schwidefsky
2011-07-07 21:36 ` Rafael J. Wysocki [this message]
2011-07-08 8:29 ` Martin Schwidefsky
2011-07-28 22:01 ` Rafael J. Wysocki
2011-08-09 15:45 ` Martin Schwidefsky
2011-08-09 19:56 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2011-08-16 14:14 [patch 0/1] [patch 0/1] " Martin Schwidefsky
2011-08-16 14:14 ` [patch 1/1] [PATCH] " Martin Schwidefsky
2011-08-16 17:56 ` Rafael J. Wysocki
2011-08-17 7:43 ` Martin Schwidefsky
2011-08-17 9:15 ` 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=201107072336.26151.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jslaby@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-s390@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=schwidefsky@de.ibm.com \
/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