Re: [RFC] ELF Relocatable x86 and x86_64 bzImages

"H. Peter Anvin" <[email protected]> writes:

> Vivek Goyal wrote:
>> Hi Eric,
>> Can't we use the x86_64 relocation approach for i386 as well? I mean keep
>> the virtual address space fixed and updating the page tables. This would
>> help in the sense that you don't have to change gdb if somebody decides to
>> debug the relocated kernel.
>> Any such tool that retrieves the symbol virtual address from vmlinux will
>> be confused.
>>
>
> I don't think this is practical given the virtual space constraints on i386
> systems.

Exactly.

Plus it is a lot of dangerous work.   Processing is a lot more
conservative.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC] ELF Relocatable x86 and x86_64 bzImages
    • From: [email protected] (Eric W. Biederman)
  • Re: [RFC] ELF Relocatable x86 and x86_64 bzImages
    • From: Vivek Goyal <[email protected]>
  • Re: [RFC] ELF Relocatable x86 and x86_64 bzImages
    • From: "H. Peter Anvin" <[email protected]>

• Prev by Date: Re: [PATCH 7 of 13] Make __FIXADDR_TOP variable to allow it to make space for a hypervisor
• Next by Date: Re: [PATCH 18/33] x86_64: Kill temp_boot_pmds
• Previous by thread: Re: [RFC] ELF Relocatable x86 and x86_64 bzImages
• Next by thread: Re: [RFC] ELF Relocatable x86 and x86_64 bzImages
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]