Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753464AbYJJWxP (ORCPT ); Fri, 10 Oct 2008 18:53:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753170AbYJJWwh (ORCPT ); Fri, 10 Oct 2008 18:52:37 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:54727 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752110AbYJJWwb (ORCPT ); Fri, 10 Oct 2008 18:52:31 -0400 From: "Rafael J. Wysocki" To: Ingo Molnar Subject: Re: [RFC][PATCH 2/2] first callers of process_deny_checkpoint() Date: Sat, 11 Oct 2008 00:57:03 +0200 User-Agent: KMail/1.9.9 Cc: Dave Hansen , "Serge E. Hallyn" , containers@lists.linux-foundation.org, arnd@arndb.de, linux-kernel@vger.kernel.org, Arjan van de Ven , Peter Zijlstra , ACPI Devel Maling List References: <20081009190405.13A253CB@kernel> <200810102153.45174.rjw@sisk.pl> <20081010195339.GA509@elte.hu> In-Reply-To: <20081010195339.GA509@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810110057.04204.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1724 Lines: 41 On Friday, 10 of October 2008, Ingo Molnar wrote: > > * Rafael J. Wysocki wrote: > > > > > Surely not ACPI-compliant. > > > > > > what do you mean? > > > > The ACPI spec says quite specifically what should be done while > > entering hibernation and during resume from hibernation. We're not > > following that in the current code, but we can (gradually) update the > > code to become ACPI-compilant in that respect. However, if we go the > > checkpointing route, I don't think that will be possible any more. > > ah, i see. I did not mean to utilize any ACPI paths but simple powerdown > or reboot. > > If we checkpoint all apps to persistent disk areas (which the checkpoint > patches in this thread are about), then we can just reboot the kernel > and forget all its state. > > That capability can be used to build a really robust hibernation > implementation IMO: we could "hibernate/kexec" over between different > kernel versions transparently. (only a small delay will be noticed by > the user - if we do it smartly with in-kernel modesetting then not even > the screen contents will be changed over this.) That actually should be called a migration of VM IMO and would be a useful functionality. Sure. Hibernation, however, generally involves the restoration of the hardware and most importantly _platform_ state which IMO is impossible without the ACPI functionality, as well as wake-up, which may depend on ACPI too. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/