Re: [PATCH] IA32 move PG0 page table within kernel data segment

"bibo,mao" <[email protected]> writes:

> Hi,
>   On i386 kernel image can compile and run at any physical address,kernel
> will dynamically establish initial page table at PG0. Currently PG0 address
> is adjacent to _end, that is to say PG0 page table is out of kernel data segment.
>  Some bootloader put initrd image next kernel data segment so that initial
> page table will overwrite initrd imagte. This patch modify this and put PG0
> table at BSS segment and free this space later.
>   This patch limited kernel image size within 64M, it is possible to modify
> ld script to remove this limit, but I am not familiar with ld script.
> 
>  Any comments is welcome.

Looks like a fragile hack. x86-64 has a imho cleaner generic solution
in e820_find_area(). I would suggest to port that over.

-Andi
-
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:
  • [PATCH] IA32 move PG0 page table within kernel data segment
    • From: "bibo,mao" <[email protected]>

• Prev by Date: Re: [KJ] [PATCH] drivers/serial/dz.c: Remove save_flags()/cli()/restore_flags()
• Next by Date: INFO: possible circular locking dependency detected
• Previous by thread: [PATCH] IA32 move PG0 page table within kernel data segment
• Next by thread: [PATCH 2.6.19-rc1] drivers/media/dvb/bt8xx/dvb-bt8xx.c: check kmalloc() return value.
• 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]