Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932656AbbFJDIQ (ORCPT ); Tue, 9 Jun 2015 23:08:16 -0400 Received: from mgwkm03.jp.fujitsu.com ([202.219.69.170]:17275 "EHLO mgwkm03.jp.fujitsu.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752669AbbFJDIH (ORCPT ); Tue, 9 Jun 2015 23:08:07 -0400 X-SecurityPolicyCheck: OK by SHieldMailChecker v2.3.2 X-SHieldMailCheckerPolicyVersion: FJ-ISEC-20150223 X-SHieldMailCheckerMailID: a7f75a1e9fa74df4899e6fbb4fd834d5 Message-ID: <5577A9FF.4040603@jp.fujitsu.com> Date: Wed, 10 Jun 2015 12:07:43 +0900 From: Kamezawa Hiroyuki User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Xishi Qiu CC: Andrew Morton , nao.horiguchi@gmail.com, Yinghai Lu , "H. Peter Anvin" , Thomas Gleixner , mingo@elte.hu, Xiexiuqi , Hanjun Guo , "Luck, Tony" , Linux MM , LKML Subject: Re: [RFC PATCH 01/12] mm: add a new config to manage the code References: <55704A7E.5030507@huawei.com> <55704B0C.1000308@huawei.com> <55768B42.80503@jp.fujitsu.com> <5576BBA5.20005@huawei.com> In-Reply-To: <5576BBA5.20005@huawei.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1445 Lines: 47 On 2015/06/09 19:10, Xishi Qiu wrote: > On 2015/6/9 14:44, Kamezawa Hiroyuki wrote: > >> On 2015/06/04 21:56, Xishi Qiu wrote: >>> This patch introduces a new config called "CONFIG_ACPI_MIRROR_MEMORY", it is >>> used to on/off the feature. >>> >>> Signed-off-by: Xishi Qiu >>> --- >>> mm/Kconfig | 8 ++++++++ >>> 1 file changed, 8 insertions(+) >>> >>> diff --git a/mm/Kconfig b/mm/Kconfig >>> index 390214d..4f2a726 100644 >>> --- a/mm/Kconfig >>> +++ b/mm/Kconfig >>> @@ -200,6 +200,14 @@ config MEMORY_HOTREMOVE >>> depends on MEMORY_HOTPLUG && ARCH_ENABLE_MEMORY_HOTREMOVE >>> depends on MIGRATION >>> >>> +config MEMORY_MIRROR >>> + bool "Address range mirroring support" >>> + depends on X86 && NUMA >>> + default y >>> + help >>> + This feature depends on hardware and firmware support. >>> + ACPI or EFI records the mirror info. >> >> default y...no runtime influence when the user doesn't use memory mirror ? >> > > It is a new feature, so how about like this: default y -> n? > It's okay to me. But it's better to check performance impact before merge because you modified core code of memory management. Thanks, -Kame -- 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/