From mboxrd@z Thu Jan 1 00:00:00 1970 From: Balbir Singh Subject: Re: [PATCH v4 4/5] mm: make processing of movable_node arch-specific Date: Tue, 11 Oct 2016 23:26:19 +1100 Message-ID: <235f2d20-cf84-08df-1fb4-08ee258fdc52@gmail.com> References: <1475778995-1420-1-git-send-email-arbab@linux.vnet.ibm.com> <1475778995-1420-5-git-send-email-arbab@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1475778995-1420-5-git-send-email-arbab@linux.vnet.ibm.com> Sender: owner-linux-mm@kvack.org To: Reza Arbab , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Rob Herring , Frank Rowand , Andrew Morton Cc: Bharata B Rao , Nathan Fontenot , Stewart Smith , Alistair Popple , "Aneesh Kumar K.V" , Tang Chen , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org, linux-mm@kvack.org List-Id: devicetree@vger.kernel.org On 07/10/16 05:36, Reza Arbab wrote: > Currently, CONFIG_MOVABLE_NODE depends on X86_64. In preparation to > enable it for other arches, we need to factor a detail which is unique > to x86 out of the generic mm code. > > Specifically, as documented in kernel-parameters.txt, the use of > "movable_node" should remain restricted to x86: > > movable_node [KNL,X86] Boot-time switch to enable the effects > of CONFIG_MOVABLE_NODE=y. See mm/Kconfig for details. > > This option tells x86 to find movable nodes identified by the ACPI SRAT. > On other arches, it would have no benefit, only the undesired side > effect of setting bottom-up memblock allocation. > > Since #ifdef CONFIG_MOVABLE_NODE will no longer be enough to restrict > this option to x86, move it to an arch-specific compilation unit > instead. > > Signed-off-by: Reza Arbab Acked-by: Balbir Singh -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org