From: ebiederm@xmission.com (Eric W. Biederman)
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Byron Stanoszek <gandalf@winds.org>,
Jeremy Jackson <jerj@coplanar.net>,
linux-kernel@vger.kernel.org
Subject: Re: Faster reboots - calling _start?
Date: 06 Apr 2002 14:57:33 -0700 [thread overview]
Message-ID: <m1hemoo5gy.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0204061201281.7190-100000@winds.org> <1745393533.1018100235@[10.10.2.3]>
"Martin J. Bligh" <Martin.Bligh@us.ibm.com> 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
next prev parent reply other threads:[~2002-04-06 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 19:13 Faster reboots (and a better way of taking crashdumps?) Martin J. Bligh
2002-04-05 20:47 ` Jeremy Jackson
2002-04-06 1:48 ` Martin J. Bligh
2002-04-06 2:55 ` Jeremy Jackson
2002-04-06 17:04 ` Faster reboots - calling _start? Byron Stanoszek
2002-04-06 20:00 ` Eric W. Biederman
2002-04-06 21:37 ` Martin J. Bligh
2002-04-06 21:57 ` Eric W. Biederman [this message]
2002-04-08 7:20 ` Faster reboots (and a better way of taking crashdumps?) Suparna Bhattacharya
2002-04-11 3:47 ` Jeremy Jackson
2002-04-11 14:28 ` Suparna Bhattacharya
2002-04-06 17:56 ` Alan Cox
2002-04-07 1:35 ` Martin J. Bligh
2002-04-06 23:27 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1hemoo5gy.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=gandalf@winds.org \
--cc=jerj@coplanar.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox