public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pm@lists.linux-foundation.org,
	Jeremy Maitin-Shepard <jbms@cmu.edu>
Subject: Re: khibernation and ACPI
Date: Thu, 4 Oct 2007 12:12:06 +0200	[thread overview]
Message-ID: <20071004101206.GI22940@elf.ucw.cz> (raw)
In-Reply-To: <1191033857.11480.47.camel@caritas-dev.intel.com>

Hi!

> > > The root filesystem is initramfs, so that, the only devices needed by kernel
> > > B is timer.
> > > e. In kernel B, put needed devices back to normal state. 
> > > f. Write memory image of kernel A out
> > > g. Put all devices in quiescent and low power state
> > > h. Execute acpi_enter_sleep_state(ACPI_STATE_S4)
> > 
> > Yes, apart from d. this looks doable.
> > 
> 
> To deal with the issue of d, the following scheme can be used:
> 
> a. Boot kernel A with ACPI on
> b. In kernel A, load the image of a new kernel B with sys_kexec_load
> c. In kernel A, put all devices in quiescent and low power state
> d. In kernel A, kexec kernel B with ACPI on (some devices may be put in
> normal state during boot)
> e. In kernel B, put all devices in quiescent and low power state
> f. In kernel B, Jump back to kernel A
> g. In kernel A, put all devices in normal state
> h. In kernel A, put all devices in low power state
> i. In kernel A, execute _PTS of ACPI
> j. In kernel A, jump to kernel B again
> k. In kernel B, put needed devices back to normal state.
> l. In kernel B, write memory image of kernel A out
> m. In kernel B, put all devices in quiescent and low power state
> n. In kernel B, Execute acpi_enter_sleep_state(ACPI_STATE_S4)

That starts looking pretty complex.

Maybe we should solve the !ACPI case first (should be useful for live
crashdumping, etc)?
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-10-04 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  9:03 khibernation and ACPI Huang, Ying
2007-09-28 15:28 ` Rafael J. Wysocki
2007-09-29  2:44   ` Huang, Ying
2007-10-04 10:12     ` Pavel Machek [this message]
2007-10-04 15:32       ` 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=20071004101206.GI22940@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=jbms@cmu.edu \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nigel@nigel.suspend2.net \
    --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