From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Alexey Starikovskiy <aystarik@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC][PATCH 3/4] swsusp: Introduce restore platform operations
Date: Tue, 22 May 2007 01:55:43 +0200 [thread overview]
Message-ID: <200705220155.44430.rjw@sisk.pl> (raw)
In-Reply-To: <20070521233848.GN10714@elf.ucw.cz>
On Tuesday, 22 May 2007 01:38, Pavel Machek wrote:
> Hi!
>
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > At least on some machines it is necessary to prepare the ACPI firmware for the
> > restoration of the system memory state from the hibernation image if the
> > "platform" mode of hibernation has been used. Namely, in that cases we need to
> > disable the GPEs before replacing the "boot" kernel with the "frozen" kernel.
> > After the restore they will be re-enabled by hibernation_ops->finish(), but if
> > the restore fails, they have to be re-enabled by the restore code explicitly.
> >
> > For this purpose we can introduce two additional hibernation operations, called
> > pre_restore() and restore_cleanup() and call them from the restore code path.
> > Still, they should be called if the "platform" mode of hibernation has been
> > used, so we need to pass the information about the hibernation mode from the
> > "frozen" kernel to the "boot" kernel in the image header.
>
> I don't quite like this one... passing flags from frozen to boot
> kernel makes it more complex.
>
> Is it really neccessary?
I think so.
> Could we do the same steps as the first thing when the frozen kernel
> wakes up?
At that time we do hibernate_ops->finish() which enables the GPEs anyway
in the right place.
> What machines does it fix?
http://bugzilla.kernel.org/show_bug.cgi?id=7887
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-21 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 22:19 [RFC][PATCH 0/4] swsusp: Fix hibernation/restore code ordering Rafael J. Wysocki
2007-05-17 22:21 ` [RFC][PATCH 1/4] swsusp: Remove incorrect code from user.c Rafael J. Wysocki
2007-05-21 23:29 ` Pavel Machek
2007-05-17 22:22 ` [RFC][PATCH 2/4] swsusp: Remove code duplication between disk.c and user.c Rafael J. Wysocki
2007-05-21 23:30 ` Pavel Machek
2007-05-17 22:24 ` [RFC][PATCH 3/4] swsusp: Introduce restore platform operations Rafael J. Wysocki
2007-05-21 23:38 ` Pavel Machek
2007-05-21 23:55 ` Rafael J. Wysocki [this message]
2007-05-22 20:03 ` Rafael J. Wysocki
2007-05-22 20:10 ` Alexey Starikovskiy
2007-05-22 20:30 ` Rafael J. Wysocki
2007-05-17 22:26 ` [RFC][PATCH 4/4] swsusp: Fix hibernation code ordering Rafael J. Wysocki
2007-05-19 8:36 ` [RFC][PATCH 4/4] swsusp: Fix hibernation code ordering (updated) Rafael J. Wysocki
2007-05-21 23:31 ` Pavel Machek
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=200705220155.44430.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=aystarik@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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