From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [linux-pm] Re: Hibernate after alarm wakes from STR Date: Wed, 11 Jul 2007 02:23:02 +0100 Message-ID: <20070711012301.GA30596@srcf.ucam.org> References: <20070330235759.GC4252@cosmic.amd.com> <200707110816.42114.nigel@nigel.suspend2.net> <20070711004549.GA30249@srcf.ucam.org> <200707111053.36590.nigel@nigel.suspend2.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([217.147.92.49]:51223 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751020AbXGKBXP (ORCPT ); Tue, 10 Jul 2007 21:23:15 -0400 Content-Disposition: inline In-Reply-To: <200707111053.36590.nigel@nigel.suspend2.net> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: nigel@suspend2.net Cc: David Brownell , linux-pm@lists.linux-foundation.org, Marcelo Tosatti , linux-acpi@vger.kernel.org, Richard Hughes , rtc-linux@googlegroups.com On Wed, Jul 11, 2007 at 10:53:35AM +1000, Nigel Cunningham wrote: > On Wednesday 11 July 2007 10:45:50 Matthew Garrett wrote: > > How are you going to shift into suspend to disk without going via > > userspace? It's quite plausible that people will want different > > configuration at that point (or, realistically, need a different set of > > workarounds...) > > This is done after writing the image, from kernel space. We do the > suspend-to-ram, and if/when we wake from that, we look at the lid switch > state before removing the image. If it's still closed, the kernel code powers > down again (this time properly) without userspace ever seeing the light of > day. Yes. I'm sort of struggling to see how this is done especially reliably - if we have separate hibernation and suspend to ram pathways, which is executed in this scenario? -- Matthew Garrett | mjg59@srcf.ucam.org