On Wed, Jun 06, 2007 at 05:42:35PM -0700, H. Peter Anvin wrote:
Jeremy Fitzhardinge wrote:
Certainly, but much harder to implement. The ELF parser needs to be
prepared to move itself around to get out of the way of the ELF file.
It's a fairly large change from how it works now.
Vivek Goyal wrote:
One would not know highest used address until ELF headers have been
parsed. May be it is two step movement. First decompress ELF.gz and
ELF parser can be at the end of decompressed data. Then it can parse
the ELF headers and move itself out of the ELF header destination
Jeremy Fitzhardinge wrote:
This patch makes the payload of the bzImage file an ELF file. In
other words, the bzImage is structured as follows:
- boot sector
- 16bit setup code
- ELF header
- decompressor
- compressed kernel
A bootloader may find the start of the ELF file by
H. Peter Anvin wrote:
I was thinking prescriptive, having the decompressor read the output
stream and interpret it as ELF. I guess a descriptive approach could be
made to work, too (I haven't really thought about that avenue of
approach), but the prescriptive model seems more powerful, at
H. Peter Anvin wrote:
It doesn't if we simply declare that a certain chunk of memory is
available to it, for the case where it runs in the native configuration.
Since it doesn't have to support *any* ELF file, just the kernel one,
that's an option.
I suppose. But given that its always
On Wednesday 06 June 2007 7:41 pm, H. Peter Anvin wrote:
This makes vmlinux (normally stripped) recoverable from the bzImage file
and so anything that is currently booting vmlinux would be serviced by
this scheme.
Would this make it sane to strip the initramfs image out of vmlinux with
Rob Landley wrote:
On Wednesday 06 June 2007 7:41 pm, H. Peter Anvin wrote:
This makes vmlinux (normally stripped) recoverable from the bzImage file
and so anything that is currently booting vmlinux would be serviced by
this scheme.
Would this make it sane to strip the initramfs image out
