From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e23smtp03.au.ibm.com (e23smtp03.au.ibm.com [202.81.31.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e23smtp03.au.ibm.com", Issuer "GeoTrust SSL CA" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 996812C0226 for ; Fri, 19 Apr 2013 12:11:34 +1000 (EST) Received: from /spool/local by e23smtp03.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 19 Apr 2013 12:03:54 +1000 Received: from d23relay04.au.ibm.com (d23relay04.au.ibm.com [9.190.234.120]) by d23dlp02.au.ibm.com (Postfix) with ESMTP id 46FC92BB0052 for ; Fri, 19 Apr 2013 12:11:00 +1000 (EST) Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.235.139]) by d23relay04.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3J1vV2g37224554 for ; Fri, 19 Apr 2013 11:57:31 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r3J2AwjY015639 for ; Fri, 19 Apr 2013 12:10:59 +1000 Message-ID: <1366337453.3250.16.camel@ThinkPad-T5421.cn.ibm.com> Subject: Re: [RFC PATCH powerpc] make CONFIG_NUMA depends on CONFIG_SMP From: Li Zhong To: Michael Ellerman Date: Fri, 19 Apr 2013 10:10:53 +0800 In-Reply-To: <20130418014559.GB8261@concordia> References: <1338370318.3637.12.camel@ThinkPad-T420> <20130418014559.GB8261@concordia> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: PowerPC email list , Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2013-04-18 at 11:46 +1000, Michael Ellerman wrote: > On Wed, May 30, 2012 at 05:31:58PM +0800, Li Zhong wrote: > > I'm not sure whether it makes sense to add this dependency to avoid > > CONFI_NUMA && !CONFIG_SMP. > > > > I want to do this because I saw some build errors on next-tree when > > compiling with CONFIG_SMP disabled, and it seems they are caused by some > > codes under the CONFIG_NUMA #ifdefs. > > This seems to make sense to me. Can you please repost with a better > changelog and a description of the actual build error you were seeing. I tried it today, but didn't find any build errors any more, guess those errors should have already been fixed. But it seems to me by disabling CONFIG_NUMA when CONFIG_SMP is disabled, could at least prevent some unnecessary code being compiled into the kernel. (After building a kernel with/without CONFIG_NUMA just now, it seems that the vmlinux is ~100K smaller without CONFIG_NUMA). I'm not sure whether this is still needed. Thanks, Zhong > > cheers >