Messages in this thread | | | Date | Mon, 23 Nov 1998 20:12:38 -0500 (EST) | From | Vladimir Dergachev <> | Subject | Re: APM "SuspendToDisk" implementation problem |
| |
On Mon, 23 Nov 1998, Alan Cox wrote:
> > Only problem with "going userspace" is: what happens if apmd is > > swapped out? Then you need to read disk in order to swap it in. But > > you can not read disk, because it is missconfigured, now... > > > > Looks like it is not the way to go. :-( > > You can't umount the disk if a binary is running off it afaik. Anyway > if it worries you link apmd static and impure then it will run from swap at > all times > You miss the point. "Suspend to disk" (or Resume button) is a feature in some computers (notebooks mostly) when the RAM is saved into a file (partition) on the harddisk and computer is turned off. Afterwards, when restarted the ram is loaded back, and the execution is continued.
The idea is that you get all your applications back in the same state.
The problem is that the settings on the harddisk/io-controller are lost and the kernel needs to reset them. Of course, you cannot rely on loading anything from disk at this time.
I think that bios is supposed to make a call before doing suspend. It may make sense (as a hack) to explicitly load needed utils into memory before allowing it to suspend. Or, better, make kernel default to the safest mode w.r.t. disk i.o. and then switch with hdparm. (this will allow apmd to load).
Vladimir Dergachev
> > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |