From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758503AbYDPItV (ORCPT ); Wed, 16 Apr 2008 04:49:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754166AbYDPItN (ORCPT ); Wed, 16 Apr 2008 04:49:13 -0400 Received: from wa-out-1112.google.com ([209.85.146.176]:39708 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753605AbYDPItM (ORCPT ); Wed, 16 Apr 2008 04:49:12 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iodifJkuXmMhsDbE1xEqKruz6mz7OKP06tQ1C190I4kmhtzlGzQn1X6EAG38Qgjkae2QAsoNHV4w66tr0ow6UzEFO0RuIVH7VXbIUwmtBbB2DcCfVPGvs6CsAcoUXLn0C7eW0lPRLbamhrAg/TdpSItk3gMdlWZlgYTDGTtTsI4= Message-ID: Date: Wed, 16 Apr 2008 16:49:11 +0800 From: "eric miao" To: "Peter Teoh" Subject: Re: RFC: Self-snapshotting in Linux Cc: LKML , "Kernel Newbies" In-Reply-To: <804dabb00804160144j25584229t6673bc182fa13b3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <804dabb00804160144j25584229t6673bc182fa13b3@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hibernation maybe ... try "echo "disk" > /sys/power/state" On Wed, Apr 16, 2008 at 4:44 PM, Peter Teoh wrote: > Sorry if this is a a crazy idea.....just be forewarned.... > > First, I would like to make a reference to VMWare's snapshot (name not > important, emphasize the idea) feature - hopefully u are familiar with > it. This is a feature whereby u can freeze the entire OS (kernel + > userspace application running) and then later reload itself next time, > continuing where it left off, without reboot from ground zero. > > Next, can I ask, is such a feature useful in Linux? Ie, able to > restart the kernel + userspace application from where u left off, the > last time round. Not JUST the normal suspend/resume feature, but > more important able to CHOOSE among the different available images for > u to resume on. Eg, u want to freeze the current 2.6.25-rc6 kernel, > save it, and then restore back the 2.6.23-rc5 image, work on it, save > it, and then restore the previous image again. All done without > virtualization as in the VMWare sense - which really is CPU intensive > and slow things down a lot. Now we can directly execute each OS > kernel image on the CPU, and since saving and restoring is quite fast > (eg, zipping up the entire physical memory before saving into > permanent storage) - I supposed this will be much faster than the > normal initialization/fsck work done normally....or did I missed out > anything? > > Essentially, to reiterate the key idea: able to snapshot the current > kernel+userspace permanent.....restore from another snapshot....and > then switch back again if needed etc.....will the implementation be > difficult...if not impossible???? > > -- > Regards, > Peter Teoh > -- > 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/ > -- Cheers - eric