[RFC] [PATCH 0/16] x86_64: Relocatable bzImage Support (V2)

Hi All,

Eric Biederman implemented the relocatable bzImage for x86_64 and posted
patches for comments quite some time back.

http://marc.theaimsgroup.com/?l=linux-kernel&m=115443019026302&w=2

We have been testing the patches in RHEL kernels since then and things are
looking up. I think this is the time that patches can be included in -mm
and get more testing done and get rest of the issues sorted out.

Eric is currently held up with other things, so I have taken his patches
and forward ported to 2.6.19-rc5-git2. Did few cleanups and fixed few
bugs as faced in our testing. I have also accomodated the review comments
received last time.

These changes make a bzImage and vmlinux relocatable hence kernel can be
loaded at and run from a non-1MB location. These changes are especially
useful for kdump where a single kernel can be used both as production
kernel and dump capture kernel hence making the life easier both for
distros and developers.

Following is a brief account of changes I have done since patches were
posted last time.

- Forward ported the changes to latest kernel.
- Extended bzImage protocol to handle relocatable kernel
- Dropped support for elf bzImage
- Dropped support for the serial debugging in decompressor code.
- Fixed a bug related to memory hotplug.
- Fixed a bug related to setting NX bit (Thanks to larry woodman)
- Fixed a bug regarding jumping to secondary_startup_64 instead of
assuming that align fills empty space with "nop".
- Fixed a bug regarding phys_base being put in initdata section.
- Fixed a but where bss was not being zeroed properly
- Reverted the change back to cotinue to compile the kernel for 2MB so
that loaders loading vmlinux directly are not broken.
- Aligned data segment to 4K boundary to make kexec using vmlinux work.
- Tested to patch for making sure suspend/resume to/from memory is working.
(Required due to ACPI wake up code changes)

Your comments/suggestions are welcome.

Thanks
Vivek
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: This is [Re:] How to improve the quality of the kernel[?].
    ... The problem are more social problems like patches Andrew has never heard ... The accepted industry standard for bug counts is basically one bug per a ... We cannot get a regression free or even bug free kernel. ... able to handle all incoming bug reports is IMHO a worthwhile and not ...
    (Linux-Kernel)
  • Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project
    ... They're only seeing janitorial-style patches hit ... a lot of the trivial patches don't come across the janitors list ... people involved with kernel development, ... fixing a bug. ...
    (Linux-Kernel)
  • Re: My thoughts on the "new development model"
    ... | The only thing that makes a kernel 'stable' is time. ... breaking your own patches!). ... | That's NOT the same as bug free software. ... | want a new feature. ...
    (Linux-Kernel)
  • The performance and behaviour of the anti-fragmentation related patches
    ... I've posted up patches that implement the two generally accepted approaches ... physical address space on the vanilla kernel because there is no effort made ... also that the huge page allocations always come from here as well. ... Vanilla Kernel List-base Kernel Zone-base Kernel Combined Kernel ...
    (Linux-Kernel)
  • Re: This is [Re:] How to improve the quality of the kernel[?].
    ... The -mm kernel already implements what your proposed PTS would do. ... If patch have no TS ID, ... Thus i can apply for example lguest patches and implement and test new ... How many open source projects use Bugzilla and how many use the Debian BTS? ...
    (Linux-Kernel)