mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Resume only part of device tree?
Date: Thu, 04 Mar 2004 15:07:16 +1300	[thread overview]
Message-ID: <1078366036.3218.64.camel@calvin.wpcb.org.au> (raw)
In-Reply-To: <1078372625.15323.57.camel@gaston>

Okay. I'll write it then. Thanks.

Nigel

On Thu, 2004-03-04 at 16:57, Benjamin Herrenschmidt wrote:
> 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.
> 
-- 


      reply	other threads:[~2004-03-04  4:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 20:03 Nigel Cunningham
2004-03-03 22:40 ` Benjamin Herrenschmidt
2004-03-04  0:48   ` Nigel Cunningham
2004-03-04  3:57     ` Benjamin Herrenschmidt
2004-03-04  2:07       ` Nigel Cunningham [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1078366036.3218.64.camel@calvin.wpcb.org.au \
    --to=ncunningham@users.sourceforge.net \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®