Messages in this thread | | | From | "Rafael J. Wysocki" <> | Subject | Re: [PATCH 0/2] Kexec jump: The first step to kexec base hibernation | Date | Fri, 13 Jul 2007 14:01:34 +0200 |
| |
On Friday, 13 July 2007 19:32, Huang, Ying wrote: > On Thu, 2007-07-12 at 20:06 -0700, david@lang.hm wrote: > > >> I agree, a stipped down hibernate kernel can be very small, not allocating > > >> this memory until it's needed is a step for the final polishing. > > > > > > I'm not sure if I agree with that. In any case, having to use two different > > > kernels for hibernation would be a big drawback. > > > > I see it as a big advantage to not have to use the main kernel for the > > suspend. please keep it as an option at least. > > Yes. It has additional bonus to make it possible to write/read image > from a program other than main kernel. For example, for a specific > mobile device product (Such as Intel MID), a customized ultra-small > program (or kernel) can be composed to write/read image. That way, the > hibernate/resume time can be reduced to minimal.
You don't need kexec for that. This is how the userland hibernation (aka uswsusp) works.
Greetings, Rafael
-- "Premature optimization is the root of all evil." - Donald Knuth - 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/
| |