From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0186.outbound.protection.outlook.com [207.46.163.186]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 256F614019F for ; Wed, 7 May 2014 07:50:01 +1000 (EST) Message-ID: <1399412988.15726.202.camel@snotra.buserror.net> Subject: Re: [PATCH 2/2 v2] powerpc: Enable NO_BOOTMEM From: Scott Wood To: Emil Medve Date: Tue, 6 May 2014 16:49:48 -0500 In-Reply-To: <1399402084-6325-2-git-send-email-Emilian.Medve@Freescale.com> References: <1399402084-6325-1-git-send-email-Emilian.Medve@Freescale.com> <1399402084-6325-2-git-send-email-Emilian.Medve@Freescale.com> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2014-05-06 at 13:48 -0500, Emil Medve wrote: > Currently bootmem is just a wrapper around memblock. This gets rid of > the wrapper code just as other ARHC(es) did: x86, arm, etc. > > For now only cover !NUMA systems/builds > > Signed-off-by: Emil Medve > --- > > v2: Acknowledge that NUMA systems/builds are not covered by this patch > > arch/powerpc/Kconfig | 3 +++ > arch/powerpc/mm/mem.c | 8 ++++++++ > 2 files changed, 11 insertions(+) > > diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig > index e099899..07b164b 100644 > --- a/arch/powerpc/Kconfig > +++ b/arch/powerpc/Kconfig > @@ -475,6 +475,9 @@ config SYS_SUPPORTS_HUGETLBFS > > source "mm/Kconfig" > > +config NO_BOOTMEM > + def_bool !NUMA This will allow a user to manually turn on CONFIG_NO_BOOTMEM in the presence of NUMA. From the changelog it sounds like this is not what you intended. What are the issues with NUMA? As is, you're not getting rid of wrapper code -- only adding ifdefs. -Scott