From: "Huang, Ying" <ying.huang@intel.com>
To: Stefan Rompf <stefan@loplof.de>
Cc: linux-pm@lists.linux-foundation.org,
"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>,
Kexec Mailing List <kexec@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] [RFC][PATCH 0/2 -mm] kexec based hibernation -v3
Date: Fri, 21 Sep 2007 16:47:11 +0800 [thread overview]
Message-ID: <1190364431.21818.186.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <200709211043.38266.stefan@loplof.de>
On Fri, 2007-09-21 at 10:43 +0200, Stefan Rompf wrote:
> Am Donnerstag, 20. September 2007 07:34 schrieb Huang, Ying:
>
> > The hibernation procedure with the patch set is as follow:
> >
> > 1. Boot a kernel A
> >
> > 2. Work under kernel A
> >
> > 3. Kexec another kernel B (crash dump enabled) in kernel A.
>
> From a short glance over current Linus' arch/i386/kernel/machine_kexec.c,
> memory for the crash dump kernel B still needs to be reserved statically when
> booting A.
>
> This is one of the biggest issues with kexec based hibernation. For the
> typical notebook user, it is totally unacceptable to reserve 16 megabytes of
> memory just to be able to suspend to disk. And given the fact that current
> distribution kernels are quite modular and require early module loading, even
> more memory might be needed.
>
> IMHO, a plan how to fix this must exist or the concept of kexec based
> hibernation is a waste of time.
This issue has been resolved. The implementation method details in
another mail with title as follow:
[RFC][PATCH 1/2 -mm] kexec based hibernation -v3: kexec jump
Best Regards,
Huang Ying
next prev parent reply other threads:[~2007-09-21 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 5:34 [RFC][PATCH 0/2 -mm] kexec based hibernation -v3 Huang, Ying
2007-09-21 8:43 ` [linux-pm] " Stefan Rompf
2007-09-21 8:47 ` Huang, Ying [this message]
2007-09-21 9:47 ` Mika Penttilä
[not found] ` <851fc09e0709210644y4a859a2bp223ef56b08a27f0@mail.gmail.com>
2007-09-21 14:56 ` Mika Penttilä
[not found] ` <851fc09e0709210813s1bb3fb02y6096c74fdc9dc35d@mail.gmail.com>
2007-09-21 15:13 ` Mika Penttilä
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=1190364431.21818.186.camel@caritas-dev.intel.com \
--to=ying.huang@intel.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=stefan@loplof.de \
/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