Software suspend - again
Posted Feb 11, 2006 12:16 UTC (Sat) by ebiederm
In reply to: Software suspend - again
Parent article: Software suspend - again
Actually the file-backed suspend to ram would work with kexec,
you do the suspend in user space (of the other kernel) then you
suspend the dump kernel to ram. We might want to do a little
trickery so the restore goes back to the primary kernel.
I don't think it is fundamentally more complicated for users but it
would be something that needs looking at.
8M/16M is more than you need that is the kind of size where
you can put a kernel and a glibc based user space in so it is easy.
Well it wouldn't be kexec that let's you access something outside
of mem=limit but /dev/mem.
kexec happens in whatever the kernels native mode is.
The LRU and that information could be an issue. I am not sufficiently
familiar with the swap suspend process to understand what needs to happen.
I think what happens is that you stop all hardware devices and processes
to get a consistent system state. Then you wake up just enough of the
system to save that state?
If that is the case kexec may be useful. Especially when used in the kdump
way kexec is just a nice wrapper around goto. :)
to post comments)