Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753414Ab3IXN1f (ORCPT ); Tue, 24 Sep 2013 09:27:35 -0400 Received: from mail-qc0-f176.google.com ([209.85.216.176]:58529 "EHLO mail-qc0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750830Ab3IXN1d (ORCPT ); Tue, 24 Sep 2013 09:27:33 -0400 Date: Tue, 24 Sep 2013 09:27:27 -0400 From: Tejun Heo To: Zhang Yanfei Cc: Zhang Yanfei , "Rafael J . Wysocki" , lenb@kernel.org, Thomas Gleixner , mingo@elte.hu, "H. Peter Anvin" , Andrew Morton , Toshi Kani , Wanpeng Li , Thomas Renninger , Yinghai Lu , Jiang Liu , Wen Congyang , Lai Jiangshan , isimatu.yasuaki@jp.fujitsu.com, izumi.taku@jp.fujitsu.com, Mel Gorman , Minchan Kim , mina86@mina86.com, gong.chen@linux.intel.com, vasilis.liaskovitis@profitbricks.com, lwoodman@redhat.com, Rik van Riel , jweiner@redhat.com, prarit@redhat.com, "x86@kernel.org" , linux-doc@vger.kernel.org, "linux-kernel@vger.kernel.org" , Linux MM , linux-acpi@vger.kernel.org, imtangchen@gmail.com Subject: Re: [PATCH 4/6] x86/mem-hotplug: Support initialize page tables bottom up Message-ID: <20130924132727.GI2366@htj.dyndns.org> References: <524162DA.30004@cn.fujitsu.com> <5241649B.3090302@cn.fujitsu.com> <20130924123340.GE2366@htj.dyndns.org> <52419264.3020409@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52419264.3020409@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1084 Lines: 28 On Tue, Sep 24, 2013 at 09:23:48PM +0800, Zhang Yanfei wrote: > > Hmm... so, this is kinda weird. We're doing it in two chunks and > > mapping memory between ISA_END_ADDRESS and kernel_end right on top of > > ISA_END_ADDRESS? Can't you give enough information to the mapping > > function so that it can map everything on top of kernel_end in single > > go? > > You mean we should call memory_map_bottom_up like this: > > memory_map_bottom_up(ISA_END_ADDRESS, end) > > right? But that wouldn't be ideal as we want the page tables above kernel image and the above would allocate it above ISA_END_ADDRESS, right? Maybe memory_map_bottom_up() should take extra parameters for where to allocate page tables at separately from the mapping range and treat it specially? Would that make the function a lot more complex? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/