Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755765AbXH0NQQ (ORCPT ); Mon, 27 Aug 2007 09:16:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752163AbXH0NQD (ORCPT ); Mon, 27 Aug 2007 09:16:03 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:4270 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750948AbXH0NQB (ORCPT ); Mon, 27 Aug 2007 09:16:01 -0400 Date: Mon, 27 Aug 2007 13:15:49 +0000 From: Pavel Machek To: "Eric W. Biederman" Cc: "Huang, Ying" , vgoyal@in.ibm.com, nigel@nigel.suspend2.net, Andrew Morton , Jeremy Maitin-Shepard , Alan Stern , linux-pm@lists.linux-foundation.org, Kexec Mailing List , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH 0/2 -mm] kexec based hibernation Message-ID: <20070827131549.GA4104@ucw.cz> References: <1188177245.3247.36.camel@caritas-dev.intel.com> <20070827050027.GB9809@in.ibm.com> <1188195529.3247.82.camel@caritas-dev.intel.com> <20070827075317.GB2060@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1532 Lines: 44 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. Well, uncompression yes, but crypto? What is that, some kind of trusted computing thingie? We do RSA for uswsusp, that may be a bit of problem for a bootloader, but I'm glad bootloaders are bloated already :-). -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/