public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: discuss@x86-64.org
Cc: pm list <linux-pm@lists.linux-foundation.org>,
	Nigel Cunningham <nigel@nigel.suspend2.net>
Subject: Re: [discuss] [RFC][PATCH -mm 2/4] Hibernation: Turn on ACPI during restore if necessary
Date: Wed, 22 Aug 2007 22:47:57 +0200	[thread overview]
Message-ID: <200708222247.57714.rjw@sisk.pl> (raw)
In-Reply-To: <20070821233629.GA3706@elf.ucw.cz>

On Wednesday, 22 August 2007 01:36, Pavel Machek wrote:
> On Tue 2007-08-21 16:39:01, Rafael J. Wysocki wrote:
> > On Tuesday, 21 August 2007 09:57, Pavel Machek wrote:
> > > Hi!
> > > 
> > > > From: Rafael J. Wysocki <rjw@sisk.pl>
> > > > 
> > > > If the boot kernel doesn't support ACPI and ACPI is not enabled by the platform
> > > > boot code, it may be possible to enable ACPI after restoring the system memory
> > > > from a hibernation image.  Implement that.
> > > 
> > > ACK... and I guess this should go in early. It is possible to test w/o
> > > rest of patches, (just pass acpi=off to resume kernel, no?),
> > 
> > Yup, that might work.
> > 
> > > and it  should get lot of testing.
> > 
> > Why do you think so?
> 
> Anything that touches acpi is almost guaranteed to produce nice
> fireworks :-). Okay, maybe I'm too paranoid.

Well, there's a catch, but it requires quite a bit more patching.

Namely, some ACPI code may be called from within CPU hotplug, so in
principle we should enable ACPI before that.  Fortunately, on contemporary SMP
machines ACPI is usually enabled by the BIOS, AFAICS, so that should not be
an issue.

Still, I have some patches that handle it, among other things.  I think I'll
just post them (tomorrow).

Greetings,
Rafael

  reply	other threads:[~2007-08-22 20:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 13:10 [RFC][PATCH -mm 0/4] Hibernation: Arbitrary boot kernel support on x86_64 Rafael J. Wysocki
2007-08-20 13:11 ` [RFC][PATCH -mm 1/4] " Rafael J. Wysocki
2007-08-21  7:57   ` Pavel Machek
2007-08-21 14:37     ` [discuss] " Rafael J. Wysocki
2007-08-21 19:30       ` Rafael J. Wysocki
2007-08-21 20:47         ` Rafael J. Wysocki
2007-08-20 13:16 ` [RFC][PATCH -mm 2/4] Hibernation: Turn on ACPI during restore if necessary Rafael J. Wysocki
2007-08-21  7:57   ` Pavel Machek
2007-08-21 14:39     ` Rafael J. Wysocki
2007-08-21 23:36       ` Pavel Machek
2007-08-22 20:47         ` Rafael J. Wysocki [this message]
2007-08-20 13:17 ` [RFC][PATCH -mm 3/4] Hibernation: Use temporary kernel text mapping during restore on x86_64 Rafael J. Wysocki
2007-08-21  7:59   ` Pavel Machek
2007-08-21 14:42     ` Rafael J. Wysocki
2007-08-20 13:18 ` [RFC][PATCH -mm 4/4] Hibernation: Pass CR3 value in hibernation header " Rafael J. Wysocki
2007-08-21  8:01   ` Pavel Machek
2007-08-21 14:46     ` 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=200708222247.57714.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=discuss@x86-64.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nigel@nigel.suspend2.net \
    /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