Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932532AbWBISXd (ORCPT ); Thu, 9 Feb 2006 13:23:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932533AbWBISXd (ORCPT ); Thu, 9 Feb 2006 13:23:33 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:2733 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S932532AbWBISXc (ORCPT ); Thu, 9 Feb 2006 13:23:32 -0500 To: Pavel Machek Cc: Dave Hansen , Kirill Korotaev , Linus Torvalds , Kirill Korotaev , Andrew Morton , Linux Kernel Mailing List , frankeh@watson.ibm.com, clg@fr.ibm.com, greg@kroah.com, alan@lxorguk.ukuu.org.uk, serue@us.ibm.com, arjan@infradead.org, Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , devel@openvz.org, Pavel Emelianov Subject: Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup) References: <43E38BD1.4070707@openvz.org> <43E3915A.2080000@sw.ru> <43E71018.8010104@sw.ru> <1139243874.6189.71.camel@localhost.localdomain> <20060208215412.GD2353@ucw.cz> From: ebiederm@xmission.com (Eric W. Biederman) Date: Thu, 09 Feb 2006 11:20:13 -0700 In-Reply-To: <20060208215412.GD2353@ucw.cz> (Pavel Machek's message of "Wed, 8 Feb 2006 21:54:13 +0000") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1161 Lines: 27 Pavel Machek writes: > Well, for now software suspend is done at very different level > (it snapshots complete kernel state), but being able to use > migration for this is certainly nice option. > > BTW you could do whole-machine-migration now with uswsusp; but you'd > need identical hardware and it would take a bit long... Right part of the goal is with doing it as we are doing it is that we can define what the interesting state is. Replacing software suspend is not an immediate goal but I think it is a worthy thing to target. In part because if we really can rip things out of the kernel store them in a portable format and restore them we will also have the ability to upgrade the kernel with out stopping user space applications... But being able to avoid the uninteresting parts, and having the policy complete controlled outside the kernel are the big wins we are shooting for. Eric - 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/