From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757759AbZCARuo (ORCPT ); Sun, 1 Mar 2009 12:50:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756632AbZCARug (ORCPT ); Sun, 1 Mar 2009 12:50:36 -0500 Received: from hera.kernel.org ([140.211.167.34]:48109 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756441AbZCARuf (ORCPT ); Sun, 1 Mar 2009 12:50:35 -0500 Message-ID: <49AACAA3.1060806@kernel.org> Date: Sun, 01 Mar 2009 09:49:23 -0800 From: Yinghai Lu User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: "H. Peter Anvin" CC: Ingo Molnar , Andrew Morton , Thomas Gleixner , Linux Kernel Mailing List , Jeremy Fitzhardinge Subject: Re: [PATCH] x86: put initial_pg_tables into bss -v2 References: <1235785882-17580-1-git-send-email-jeremy@goop.org> <1235785882-17580-4-git-send-email-jeremy@goop.org> <86802c440902272302n3787b2bex3741b46a372a19b0@mail.gmail.com> <49A8E235.6010900@goop.org> <20090228071534.GB9351@elte.hu> <49A8EA1A.50802@kernel.org> <49A8ED3D.1060704@kernel.org> <49A8F319.3030802@goop.org> <49A9E392.6090004@kernel.org> <49AA47D2.4020804@kernel.org> <49AA5356.3050602@zytor.com> In-Reply-To: <49AA5356.3050602@zytor.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org H. Peter Anvin wrote: > Yinghai Lu wrote: >> Impact: cleanup >> >> Don't use ram after _end blindly for pagetables. >> put those pg table into bss >> >> also remove init_pg_tables_start/end tricks all around >> >> v2: keep initial page table up to 512M only. >> > > I really, REALLY, don't like this. This is going right back to the > situation which we had before the dynamically generated page tables. We > now have yet another hardcoded limit, and big chunk of wasted memory in > case we don't need to allocate it all. that limit is there in for 64 too. aka 512M direct mapping. (need 1Mbytes space for page tables) we can get rid of that limit: with careful link sequence to make sure that code init_memory_mapping and before is some fixed range. YH