From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1W0MUS-00048w-T8 for kexec@lists.infradead.org; Tue, 07 Jan 2014 02:34:01 +0000 Date: Tue, 7 Jan 2014 10:34:06 +0800 From: Dave Young Subject: kexec: reuse 1st kernel as kexec/kdump kernel? Message-ID: <20140107023405.GC3967@dhcp-16-126.nay.redhat.com> MIME-Version: 1.0 Content-Disposition: inline List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org Cc: ebiederm@xmission.com, vgoyal@redhat.com, hpa@zytor.com Hi, all I have a question in mind: can we copy and prepare kexec kernel while normal booting? Just like below wild idea: Kernel uncompress itself (assume kernel is relocatable) -> copy the kernel image somewhere for backup -> reserver crashkernel memory -> copy the backuped kernel image/initrd image to reserved memory -> copy the purgatory which can be embedded in elf section? -> prepare the e820 memory ranges which is for kdump kernel So userspace only need to call kexec reboot, kexec_load is not necessary. The initrd for kdump should be different, but we can add some different logic which will be only for kdump and it can be skipped in normal boot. Is it doable? Thanks Dave _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec