All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC][PATCH 0/11] i386: Relocatable BzImage (V3)
@ 2006-10-23 19:24 Vivek Goyal
  2006-10-23 19:26 ` [PATCH 1/11] i386: Distinguish absolute symbols Vivek Goyal
                   ` (11 more replies)
  0 siblings, 12 replies; 17+ messages in thread
From: Vivek Goyal @ 2006-10-23 19:24 UTC (permalink / raw)
  To: linux kernel mailing list
  Cc: Reloc Kernel List, ebiederm, akpm, ak, hpa, magnus.damm, lwang,
	dzickus, maneesh

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

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2006-11-06 16:36 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-23 19:24 [RFC][PATCH 0/11] i386: Relocatable BzImage (V3) Vivek Goyal
2006-10-23 19:26 ` [PATCH 1/11] i386: Distinguish absolute symbols Vivek Goyal
2006-10-23 19:29 ` [PATCH 2/11] i386: Remove unnecessary ALIGN() in vmlinux.lds.S Vivek Goyal
2006-10-23 19:30 ` [PATCH 3/11] i386: Force data segment to be 4K aligned Vivek Goyal
2006-10-23 19:32 ` [PATCH 4/11] i386: define __pa_symbol() Vivek Goyal
2006-10-23 19:33 ` [PATCH 5/11] i386: Reserve kernel memory starting from _text Vivek Goyal
2006-10-23 19:36 ` [PATCH 6/11] i386: CONFIG_PHYSICAL_START cleanup Vivek Goyal
2006-10-23 19:37 ` [PATCH 7/11] i386: Kallsyms generate relocatable symbols Vivek Goyal
2006-11-06 14:48   ` Haavard Skinnemoen
2006-11-06 16:03     ` Vivek Goyal
2006-11-06 16:13       ` Haavard Skinnemoen
2006-11-06 16:34     ` H. Peter Anvin
2006-10-23 19:39 ` [PATCH 8/11] i386: Relocatable kernel support Vivek Goyal
2006-10-23 19:40 ` [PATCH 9/11] i386: Warn upon absolute relocations being present Vivek Goyal
2006-10-23 19:42 ` [PATCH 10/11] i386: Implement CONFIG_PHYSICAL_ALIGN Vivek Goyal
2006-10-23 19:44 ` [PATCH 11/11] i386: Extend bzImage protocol for relocatable protected mode kernel Vivek Goyal
2006-10-24 13:44 ` [RFC][PATCH 0/11] i386: Relocatable BzImage (V3) Andi Kleen

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.