linux-kernel - Re: [PATCH] x86: Construct 32 bit boot time page tables in native format.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080122100509.GC5722@elte.hu>
Date:	Tue, 22 Jan 2008 11:05:09 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Ian Campbell <ijc@...lion.org.uk>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] x86: Construct 32 bit boot time page tables in native
	format.


* H. Peter Anvin <hpa@...or.com> wrote:

> I was thinking about this yesterday, and it seems to me that there are 
> two cleaner options here...
>
> - either we should put in the full machinery to be able to run C code 
> compiled with -fPIC/-fPIE before paging is enabled.  Unfortunately gcc 
> generates R_386_GOT32 relocations for external references even with 
> -fPIE, so we'll have to put in some code to adjust the GOT (easy 
> enough to do.)

i'd _love_ to have this approach instead of the assembly routines. While 
'constructing pagetables' might not look like a big deal in isolation - 
C is still 10 times more programmable than assembly. Pushing more of the 
early boot code into a sane, non-assembly environment will have positive 
long-term effects all across.

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