From: ebiederm@xmission.com (Eric W. Biederman)
To: andersen@codepoet.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: Linux rebooting directly into linux.
Date: 14 Nov 2000 07:59:18 -0700 [thread overview]
Message-ID: <m1bsvia9bt.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m17l6deey7.fsf@frodo.biederman.org> <20001114011331.B1496@codepoet.org>
In-Reply-To: Erik Andersen's message of "Tue, 14 Nov 2000 01:13:32 -0700"
Erik Andersen <andersen@codepoet.org> writes:
> On Thu Nov 09, 2000 at 01:18:24AM -0700, Eric W. Biederman wrote:
> >
> > I have recently developed a patch that allows linux to directly boot
> > into another linux kernel.
>
> Looks very cool. I'm curious about your decision to use ELF images. This
> makes it much less conveinient to use due to the kernel postprocessing, and
> makes it that the kernel binary from which you initially boot is not
> necessirily the same as the binary that you re-boot into.
The decision here was that I needed to pass a vector of
<physical address, length, data> pairs. The elf program header
is dead simple and provides it. So I either had to invent a
complicated argument passing mechanism for a syscall or have the
kernel parse a file.
> Wouldn't it be more reasonable to simply try to exec whatever file is provided?
> If the concern is initrds; they can be simply pasted into the kernel binary.
That's exactly what my preprocessing does.
vmlinux is also an elf binary. As is arch/i386/boot/bvmlinux but it
is compressed.
All mkelfImage does is the pasting of initrd's, command lines,
and just a touch of argument conversion code.
What I don't do deliberately is allow or need setup.S which does
syscalls to run. All it does are BIOS calls, and store them in a
nasty data structure. I have replaced that data structure with
something that is maintainable.
I would like very much to not need mkelfImage. However that
requires further changes to the kernel, and I cannot boot an unpatched
kernel with that method.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-15 10:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 8:18 Q: Linux rebooting directly into linux Eric W. Biederman
[not found] ` <3A0ABB0C.99075A61@holly-springs.nc.us>
2000-11-11 19:46 ` Eric W. Biederman
2000-11-11 22:46 ` Adam Lazur
2000-11-12 0:06 ` Eric W. Biederman
[not found] ` <20001109113524.C14133@animx.eu.org>
2000-11-11 20:05 ` Eric W. Biederman
2000-11-11 20:33 ` H. Peter Anvin
2000-11-12 0:09 ` Eric W. Biederman
2000-11-12 0:32 ` H. Peter Anvin
2000-11-12 6:31 ` Eric W. Biederman
2000-11-11 22:11 ` Adam Lazur
2000-11-12 0:00 ` Eric W. Biederman
2000-11-14 14:49 ` Werner Almesberger
2000-11-16 17:33 ` Eric W. Biederman
2000-11-19 2:24 ` Werner Almesberger
2000-11-19 7:20 ` Eric W. Biederman
2000-11-19 13:25 ` Werner Almesberger
2000-11-19 20:14 ` Eric W. Biederman
2001-01-18 16:18 ` Eric W. Biederman
2000-11-14 8:13 ` Erik Andersen
2000-11-14 14:59 ` Eric W. Biederman [this message]
2000-11-15 23:30 ` Erik Andersen
2000-11-16 6:19 ` 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=m1bsvia9bt.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=andersen@codepoet.org \
--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