public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "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 3/3 -mm] kexec based hibernation -v6: kexec hibernate/resume
Date: Wed, 21 Nov 2007 16:05:06 +0800	[thread overview]
Message-ID: <1195632306.29280.7.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <200711210100.32631.rjw@sisk.pl>

On Wed, 2007-11-21 at 01:00 +0100, Rafael J. Wysocki wrote:
> On Tuesday, 20 of November 2007, Huang, Ying wrote:
> > On Tue, 2007-11-20 at 03:24 +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, 20 of November 2007, Huang, Ying wrote:
> > > > On Mon, 2007-11-19 at 19:22 +0100, Rafael J. Wysocki wrote:
> > > > > > +#ifdef CONFIG_KEXEC
> > > > > > +static void kexec_hibernate_power_down(void)
> > > > > > +{
> > > > > > +	switch (hibernation_mode) {
> > > > > > +	case HIBERNATION_TEST:
> > > > > > +	case HIBERNATION_TESTPROC:
> > > > > > +		break;
> > > > > > +	case HIBERNATION_REBOOT:
> > > > > > +		machine_restart(NULL);
> > > > > > +		break;
> > > > > > +	case HIBERNATION_PLATFORM:
> > > > > > +		if (!hibernation_ops)
> > > > > > +			break;
> > > > > > +		hibernation_ops->enter();
> > > > > 
> > > > > hibernation_platform_enter() should be used here (as of the current mainline).
> > > > 
> > > > The power_down will be called with interrupt disabled, device suspended,
> > > > non-boot CPU disabled. But the latest hibernate_platform_enter calls the
> > > > device_suspend, disable_nonboot_cpus etc function. So, I use
> > > > hibernation_ops->enter() directly instead of
> > > > hibernation_platform_enter().
> > > 
> > > Hm, you need to call device_power_down(PMSG_SUSPEND) before
> > > hibernation_ops->enter().
> > > 
> > > Also, all of the ACPI global calls need to be carried out before that and the
> > > devices should be suspended rather than shut down in that case.
> > > 
> > > That's why hibernation_platform_enter() has been introduced, BTW.
> > 
> > Situation is a little different between u/swsusp and khiberantion.
> > 
> > u/swsusp:
> > 
> > platform_start();
> > suspend console();
> > device_suspend(PMSG_FREEZE);
> > platform_pre_snapshot();
> > disable_nonboot_cpus();
> > local_irq_disable();
> > device_power_down(PMSG_FREEZE);
> > /* create snapshot */
> > device_power_up();
> > local_irq_enable();
> > enable_nonboot_cpus();
> > platform_finish();
> > device_resume();
> > resume_console();
> > /* write the image out */
> > hibernation_ops->start();
> > suspend_console();
> > device_suspend(PMSG_SUSPEND);
> > hibernation_ops->prepare();
> > disable_nonboot_cpus();
> > local_irq_disable();
> > device_power_down(PMSG_SUSPEND);
> > hibernation_ops->enter();
> > 
> > khibernation:
> > 
> > suspend_console();
> > platform_start();
> > device_suspend(PMSG_FREEZE);
> > platform_pre_snapshot();
> > disable_nonboot_cpus();
> > local_irq_disable();
> > device_power_down(PMSG_FREEZE);
> > /* jump to kexeced (hibernating) kernel */
> > /* in kexeced kernel */
> > device_power_up();
> > local_irq_eanble();
> > enable_nonboot_cpus();
> 
> You should call platform_finish() here, or device_resume() will not work
> appropriately on some systems.
> 
> However, after platform_finish() has been executed, the ACPI firmware will
> assume that the hibernation has been canceled, so you need to tell it that
> you'd like to go into the low power state after all.
> 
> > device_resume();
> > resume_console();
> > /* write the image */
> 
> For this reason, you have to call hibernation_ops->start() once again
> and the other functions like in the swsusp case, in that order.
> 
> > suspend_console();
> > device_suspend(PMSG_FREEZE);
> > disable_nonboot_cpus();
> > local_irq_disable();
> > device_power_down(PMSG_FREEZE);
> > /* jump to original (hibernated) kernel */
> 
> This looks too fragile to my eyes.
> 
> Why don't you call hibernation_ops->enter() directly from the "kexeced" kernel?

I don't know whether there are ACPI global state inside Linux kernel. So
I restrict all ACPI method calling in original kernel. If the ACPI
global state in Linux kernel is not a issue, I can call
hibernation_ops->enter() directly in the "kexeced" kernel.

Best Regards,
Huang Ying

  reply	other threads:[~2007-11-21  8:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  7:02 [PATCH 3/3 -mm] kexec based hibernation -v6: kexec hibernate/resume Huang, Ying
2007-11-19 18:22 ` Rafael J. Wysocki
2007-11-20  1:56   ` Huang, Ying
2007-11-20  2:24     ` Rafael J. Wysocki
2007-11-20  2:50       ` Huang, Ying
2007-11-20 14:58         ` [linux-pm] " Alan Stern
2007-11-21  0:00           ` Rafael J. Wysocki
2007-11-21  0:00         ` Rafael J. Wysocki
2007-11-21  8:05           ` Huang, Ying [this message]
2007-11-21 20:09             ` 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=1195632306.29280.7.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=rjw@sisk.pl \
    /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