RFC i386: Relocatable BzImage (V3)
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest11 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/11 | i386: Distinguish absolute symbolsarch/ include/ | +63 | 0 replies | |
| 2/11 | i386: Remove unnecessary ALIGN() in vmlinux.lds.Sarch/ | +6 | 0 replies | |
| 3/11 | i386: Force data segment to be 4K alignedarch/ | +1 | 0 replies | |
| 4/11 | i386: define __pa_symbol()include/ | +3 | 0 replies | |
| 5/11 | i386: Reserve kernel memory starting from _textarch/ | +2 | 0 replies | |
| 6/11 | i386: CONFIG_PHYSICAL_START cleanuparch/ arch/ arch/ +1 more | +7 | 0 replies | |
| 7/11 | i386: Kallsyms generate relocatable symbolsarch/ arch/ arch/ +5 more | +24 | 4 replies | |
| 8/11 | i386: Relocatable kernel supportarch/ arch/ arch/ +7 more | +926 | 0 replies | |
| 9/11 | i386: Warn upon absolute relocations being presentarch/ arch/ | +73 | 0 replies | |
| 10/11 | i386: Implement CONFIG_PHYSICAL_ALIGNarch/ arch/ arch/ +2 more | +43 | 0 replies | |
| 11/11 | i386: Extend bzImage protocol for relocatable protected mode kernelDocumentation/ arch/ | +16 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/11] i386: Relocatable BzImage (V3)
Hi,
Here is the third attempt on implementing relocatable bzImage for i386. Eric has done all the ground work and I am just giving it final finish. Generated patches against (2.6.19-rc2-git7).
V2 ran into issues with lilo on Andrew's machine. I can't reproduce the problem. For the sake of simpilicity, I have dropped the bit which added and ELF header to bzImage. Instead, I have extended the bzImage protocol to enable boot loaders to load protected mode kernel at a non 1MB address. Hopefully this should not break any existing behaviour.
This functionality is especially useful for kdump where a single kernel can be used both as production kernel and dump capture kernel and distors don't have to maintain an additional kernel just for capturing the dump.
I have tested it with grub (.97) and lilo (lilo 22.7.3).
Note: One has to upgrade the binutils if you want to use
CONFIG_RELOCATABLE=y. Previous ld version will make section relative symbols absolute, if section containing the symbols has zero size. These absolute symbols are not relocated. This issue has been fixed in latest binutils. I am using the one built on 09th octoer 2006 and it works fine for me.
Chages since version V2
----------------------
- Dropped adding and ELF header to bzImage.
- Extended bzImage protocol for relocatable bzImage (version 2.05)
- Added support to display warning message at compilation time if relocations relative to absolute symbols are present.
- Fixed a bug where some intermediate files were not being cleaned up by "make clean"
- Avoid building vmlinux.bin.all if CONFIG_RELOCATABLE is not set.
Looking forward for your suggestions and any test results.
Thanks
Vivek