[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <988792.74810.qm@web26913.mail.ukl.yahoo.com>
Date: Tue, 6 Feb 2007 18:39:11 +0000 (GMT)
From: Etienne Lorrain <etienne_lorrain@...oo.fr>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, vgoyal@...ibm.com,
linux-kernel@...r.kernel.org
Subject: Re : Re : [PATCH] Compressed ia32 ELF file generation for loading by Gujin 1/3
Eric W. Biederman wrote:
> Etienne Lorrain <etienne_lorrain@...oo.fr> writes:
> > 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.
Well, if the function called at offset 0 in the real-mode section return
non zero, that is probably an error - that is Gujin interface, but do not ask
me to change other bootloaders to handle that.
This function is called with few parameters, one is a string pointer
if the function do not want to print the problem report itself.
The function is called with an offset of zero in its own intel segment.
> > 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.
Well, for my defense, if Gujin do not find the real mode code in the program
header it search for it in the section table, if the program header cannot be
modified for some reason. There may be some issues if that ELF file is
"stripped" but it seems to work on my side.
> > 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.
There was still a test not that long ago (in the code I am not executing) - but
I was wrong to bring this point forward.
> With the right delicacy, and preserving backwards compatibility
> with existing bootloaders I think we can achieve things.
Well, you can generate with the proposed patch and boot with SYSLINUX,
Grub and LILO, but trying to clean Linux real-mode code is where I begun.
> The big issue is that sometimes bootloaders are a little bit brittle.
> Eric
I like to think mine is more stable - maybe I am a dreamer...
I do not compete on network booting neither.
Etienne.
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists