Messages in this thread | | | From | (Eric W. Biederman) | Subject | Re: [RFC][PATCH 0/2 -mm] kexec based hibernation | Date | Mon, 27 Aug 2007 07:05:41 -0600 |
| |
Pavel Machek <pavel@ucw.cz> writes:
> Hi! > >> > Does this make sense? >> >> Yes, this is a sensible optimization. But I think it may be better to >> make bootloader load kernel D directly into a specified memory location. >> For example, we can add a option to "kernel" command of grub. >> >> And, I think we can do more in bootloader. Such as we can prepare >> two > > Yes, that would be nice. > > It will mean quite a bit of work, but I guess it should be the long > term goal. Loading restore kernel directly from bootloader means: > > 1) it is fast -- no need to boot another kernel > > 2) it is "classical" way of doing things > > On the other hand, we loose flexibility that way: > > 1) it locks you onto one bootloader > > 2) you no longer have userland there to do uncompression, decryption, > etc..
True although for the uncompression and decryption those aren't exactly foreign requirements for bootloaders.
Eric - 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/
| |