Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 6 Apr 2002 17:04:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 6 Apr 2002 17:04:10 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:32569 "EHLO frodo.biederman.org") by vger.kernel.org with ESMTP id ; Sat, 6 Apr 2002 17:04:09 -0500 To: "Martin J. Bligh" Cc: Byron Stanoszek , Jeremy Jackson , linux-kernel@vger.kernel.org Subject: Re: Faster reboots - calling _start? In-Reply-To: <1745393533.1018100235@[10.10.2.3]> From: ebiederm@xmission.com (Eric W. Biederman) Date: 06 Apr 2002 14:57:33 -0700 Message-ID: Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Martin J. Bligh" writes: > > Wouldn't it be easier to just ljmp to the start address of the kernel in > > memory (the address after the bootloader has done its thing), effectively > > restarting the kernel from line 1? Or is tehre an issue with some > > hardware being in an invalid state when doing this? > > Two issues with that: > > 1. I want to be able to boot a different kernel on reboot - this > is a development machine. > > 2. I believe we free all the __init stuff around the end of > start_kernel, so the initial functions and data just aren't > there any more ... of course that could be changed, but it's > both a more major change than I really want to do, and it still > doesn't solve (1) ;-) Seriously check out my code it should just work unless there are special apic shutdown rules for NUMAQ machines. 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/