Hi. On Tue, 2007-05-29 at 14:03 +0200, Rafael J. Wysocki wrote: > 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. I'd rather be sure. It will be extra code, but reliability is important. > > > - to copy the nosave data to a 'safe' page. > > > > > > What else? > > > > page directories need to be on a safe place, too. > > They are already. Yeah - that's why I ignored them. Regards, Nigel
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- [2.6.21.1] resume doesn't run suspended kernel?
- From: Bill Davidsen <[email protected]>
- Re: [2.6.21.1] resume doesn't run suspended kernel?
- From: Nigel Cunningham <[email protected]>
- Re: [2.6.21.1] resume doesn't run suspended kernel?
- From: Pavel Machek <[email protected]>
- Re: [2.6.21.1] resume doesn't run suspended kernel?
- From: "Rafael J. Wysocki" <[email protected]>
- [2.6.21.1] resume doesn't run suspended kernel?
- Prev by Date: Re: [PATCH] Update Documentation/block/barrier.txt
- Next by Date: Re: Block devices and barriers
- Previous by thread: Re: [2.6.21.1] resume doesn't run suspended kernel?
- Next by thread: Re: [2.6.21.1] resume doesn't run suspended kernel?
- Index(es):