Subject: Re: Resume only part of device tree?
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <1078361326.3203.47.camel@calvin.wpcb.org.au>
References: <1078344202.3203.22.camel@calvin.wpcb.org.au>
	 <1078353622.15320.25.camel@gaston>
	 <1078361326.3203.47.camel@calvin.wpcb.org.au>
Content-Type: text/plain
Message-Id: <1078372625.15323.57.camel@gaston>
Mime-Version: 1.0
Date: Thu, 04 Mar 2004 14:57:06 +1100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1092
Lines: 25

On Thu, 2004-03-04 at 11:48, Nigel Cunningham wrote:
> Hi.
> 
> My implementation saved the image in two parts. 'Pageset 2' contains the
> LRU pages (active & inactive lists). 'Pageset 1' contains all other data
> to be saved. At resume time, I read pageset 1 and copy the original
> kernel data back. Then I want to resume the storage devices and read
> pageset 2 before resuming all devices and waking everything else up. It
> would also be good to not resume all devices when writing the state to
> the swap partition, but I have other means of ensuring the consistency
> of the image that mean I'm not so worried then.

I don't see any good way to do that at this point. With a tree
structure, it would be possible to revive only the parents of
the storage device you are concerned in, but at this point, we
don't have this possibility

Ben.


-
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/