From: Andi Kleen <ak@suse.de>
To: "bibo,mao" <bibo.mao@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IA32 move PG0 page table within kernel data segment
Date: 16 Oct 2006 16:04:25 +0200 [thread overview]
Message-ID: <p73k630cq6u.fsf@verdi.suse.de> (raw)
In-Reply-To: <4529E2BE.1060506@intel.com>
"bibo,mao" <bibo.mao@intel.com> 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
prev parent reply other threads:[~2006-10-16 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 5:48 [PATCH] IA32 move PG0 page table within kernel data segment bibo,mao
2006-10-16 14:04 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73k630cq6u.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=bibo.mao@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox