From: "huang ying" <huang.ying.caritas@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Huang, Ying" <ying.huang@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Pavel Machek" <pavel@ucw.cz>,
nigel@nigel.suspend2.net,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jeremy Maitin-Shepard" <jbms@cmu.edu>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
"Kexec Mailing List" <kexec@lists.infradead.org>
Subject: Re: [PATCH 4/4 -mm] kexec based hibernation -v7 : kimgcore
Date: Fri, 7 Dec 2007 21:56:18 +0800 [thread overview]
Message-ID: <851fc09e0712070556g13741a0vc56348ffbbb57a1d@mail.gmail.com> (raw)
In-Reply-To: <200712071333.06836.rjw@sisk.pl>
On Dec 7, 2007 8:33 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Friday, 7 of December 2007, Huang, Ying wrote:
> > This patch adds a file in proc file system to access the loaded
> > kexec_image, which may contains the memory image of kexeced
> > system. This can be used by kexec based hibernation to create a file
> > image of hibernating kernel, so that a kernel booting process is not
> > needed for each hibernating.
>
> Hm, I'm not sure what you mean.
>
> Can you explain a bit, please?
The normal kexec based hibernation procedure is as follow:
1. kexec_load the kernel image and initramfs
2. jump to hibernating kernel
3. the normal boot process of kexeced kernel
4. jump back to hibernated kernel
5. execute ACPI methods
6. jump to hibernating kernel
7. write memory image of hibernated kernel
8. go to ACPI S4 state
With kimgcore:
A. Prepare a memory image of hibernation kernel:
A.1 kexec_load the kernel image and initramfs
A.2 jump to hibernating kernel
A.3 the normal boot process of kexeced kernel
A.4 jump back to hibernated kernel
A.5 save the memory image of hibernating kernel via kimgcore
The normal hibernate process is as follow:
1. kexec load the kimgcore of hibernatin kernel
2. jump to the hibernating kernel
3. execute ACPI methods
4. jump to hibernating kernel
5. write memory image of hibernated kernel
6. go to ACPI S4 state
So the boot process of hibernating kernel needs only once unless the
hardware configuration is changed.
Best Regards,
Huang Ying
prev parent reply other threads:[~2007-12-07 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 15:53 Huang, Ying
2007-12-07 12:33 ` Rafael J. Wysocki
2007-12-07 13:56 ` huang ying [this message]
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=851fc09e0712070556g13741a0vc56348ffbbb57a1d@mail.gmail.com \
--to=huang.ying.caritas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jbms@cmu.edu \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=ying.huang@intel.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
all inboxes | Powered by JetHome®