Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753400Ab2KTDtL (ORCPT ); Mon, 19 Nov 2012 22:49:11 -0500 Received: from szxga02-in.huawei.com ([119.145.14.65]:14150 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753079Ab2KTDtJ (ORCPT ); Mon, 19 Nov 2012 22:49:09 -0500 Message-ID: <50AAFD0D.2010003@huawei.com> Date: Tue, 20 Nov 2012 11:46:21 +0800 From: Jiang Liu User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Jaegeuk Hanse CC: Jiang Liu , Andrew Morton , Wen Congyang , David Rientjes , Maciej Rutecki , Chris Clayton , "Rafael J . Wysocki" , Mel Gorman , Minchan Kim , KAMEZAWA Hiroyuki , Michal Hocko , Jianguo Wu , , Subject: Re: [RFT PATCH v1 0/5] fix up inaccurate zone->present_pages References: <20121115112454.e582a033.akpm@linux-foundation.org> <1353254850-27336-1-git-send-email-jiang.liu@huawei.com> <50AAE72E.3090101@gmail.com> <50AAEE61.2090504@huawei.com> <50AAF6F3.8010203@gmail.com> In-Reply-To: <50AAF6F3.8010203@gmail.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.108.108.229] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1334 Lines: 29 On 2012-11-20 11:20, Jaegeuk Hanse wrote: > On 11/20/2012 10:43 AM, Jiang Liu wrote: >> On 2012-11-20 10:13, Jaegeuk Hanse wrote: >>> On 11/19/2012 12:07 AM, Jiang Liu wrote: >> Hi Jaegeuk, >> Thanks for review this patch set. >> Currently x86/x86_64/Sparc have been converted to use nobootmem.c, >> and other Arches still use bootmem.c. So need to test it on other Arches, >> such as ARM etc. Yesterday we have tested it patchset on an Itanium platform, >> so bootmem.c should work as expected too. > > Hi Jiang, > > If there are any codes changed in x86/x86_64 to meet nobootmem.c logic? I mean if remove > config NO_BOOTMEM > def_bool y > in arch/x86/Kconfig, whether x86/x86_64 can take advantage of bootmem.c or not. There are code change in x86/x86_64 arch directory to convert from bootmem.c to nobootmem.c, so you can't simply comment out NO_BOOTMEM Kconfig item. There are differences in APIs for bootmem.c and nobootmem.c. For example, free_low_memory_core_early() is only provided by nobootmem.c and init_bootmem_node() is only provided by bootmem.c. Thanks! -- 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/