From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Subject: Re: [2.6.21.1] resume doesn't run suspended kernel?
Date: Tue, 29 May 2007 14:03:07 +0200
User-Agent: KMail/1.9.5
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>,
       Bill Davidsen <davidsen@tmr.com>,
       Linux Kernel M/L <linux-kernel@vger.kernel.org>
References: <4658B7DD.3060309@tmr.com> <1180392482.4149.15.camel@nigel.suspend2.net> <20070529112952.GA23046@elf.ucw.cz>
In-Reply-To: <20070529112952.GA23046@elf.ucw.cz>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705291403.09773.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 999
Lines: 31

On Tuesday, 29 May 2007 13:29, Pavel Machek wrote:
> Hi!
> 
> > > Yup.  Don't we do something like this for the (ACPI-based) suspend to RAM
> > > already?
> > 
> > Yeah, I was thinking about this overnight too. It should be doable. In
> > addition to what we already do, I think you'd want:
> > 
> > - to copy the assembly to do the copying to a safe page;
> > - to put the location of the cpu state that was saved in the image
> > header so that it can be used after the data is copied back;
> 
> ...alternatively, we can just rely on copy routine (and its data) not
> changing frequently.
> 
> > - to copy the nosave data to a 'safe' page.
> > 
> > What else?
> 
> page directories need to be on a safe place, too.

They are already.

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