From: ebiederm@xmission.com (Eric W. Biederman)
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
vgoyal@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Re : [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3
Date: Tue, 06 Feb 2007 11:12:39 -0700 [thread overview]
Message-ID: <m1lkjbtaso.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <957176.28334.qm@web26903.mail.ukl.yahoo.com> (Etienne Lorrain's message of "Tue, 6 Feb 2007 17:23:55 +0000 (GMT)")
Etienne Lorrain <etienne_lorrain@yahoo.fr> writes:
> H. Peter Anvin wrote:
>> Actually, as far as I can see, he has re-invented having a real-mode
>> code chunk which then gets run before the protected-mode kernel. We
>> already have that!
>
> I did not claim to have invented anything there, this is just a quite
> simple C code to execute instead of the current real mode assembly:
> it is a rewrite with obvious advantages/disadvantages.
> New features are more that this real-mode function can return an error
> to the bootloader to tell something to the user, so the user can select
> another kernel with the right processor, another video mode... with
> clean error messages - not a crash dump because this assembly
> instruction is not for that processor.
Having an error handling compatibility that is backwards compatible sounds
interesting.
> I am still saying that the bootloader knows the root filesystem to
> be used by the kernel it loads, and that ELF is a clean format to
> store different sections to be loaded into memory at predefined
> addresses.
Yes. Although when you think sections instead of segments I'm a little
worried.
> Also there isn't any more kernel size limit.
I think as HPA points out we have gotten past that a long time
ago with the bzImage format.
With the right delicacy, and preserving backwards compatibility
with existing bootloaders I think we can achieve things.
The big issue is that sometimes bootloaders are a little bit brittle.
Eric
next prev parent reply other threads:[~2007-02-06 18:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 17:23 Etienne Lorrain
2007-02-06 17:34 ` H. Peter Anvin
2007-02-06 18:12 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-11 20:49 RE : " Eric W. Biederman
2007-02-12 10:42 ` Etienne Lorrain
2007-02-12 12:29 ` Eric W. Biederman
2007-02-12 13:58 ` Etienne Lorrain
2007-02-12 14:06 ` H. Peter Anvin
2007-02-12 19:47 ` Eric W. Biederman
2007-02-08 13:10 Etienne Lorrain
2007-02-09 5:59 ` Vivek Goyal
2007-02-09 13:04 ` Etienne Lorrain
2007-02-09 19:42 ` Eric W. Biederman
2007-02-08 9:48 Etienne Lorrain
2007-02-08 11:20 ` Eric W. Biederman
2007-02-08 11:37 ` Vivek Goyal
2007-02-08 12:10 ` Eric W. Biederman
2007-02-07 14:29 Etienne Lorrain
2007-02-07 17:12 ` H. Peter Anvin
2007-02-06 13:23 Etienne Lorrain
2007-02-06 13:12 Etienne Lorrain
2007-02-07 6:44 ` Vivek Goyal
2007-02-06 12:49 Etienne Lorrain
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=m1lkjbtaso.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=etienne_lorrain@yahoo.fr \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
/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
all inboxes | Powered by JetHome®