Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932524AbbFHPRG (ORCPT <rfc822;w@1wt.eu>);
	Mon, 8 Jun 2015 11:17:06 -0400
Received: from mga11.intel.com ([192.55.52.93]:24861 "EHLO mga11.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752670AbbFHPRD (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 8 Jun 2015 11:17:03 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.13,574,1427785200"; 
   d="scan'208";a="739455295"
From: "Luck, Tony" <tony.luck@intel.com>
To: Leon Romanovsky <leon@leon.nu>, Xishi Qiu <qiuxishi@huawei.com>
CC: Andrew Morton <akpm@linux-foundation.org>,
        "nao.horiguchi@gmail.com" <nao.horiguchi@gmail.com>,
        Yinghai Lu <yinghai@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
        Thomas Gleixner <tglx@linutronix.de>, "mingo@elte.hu" <mingo@elte.hu>,
        Xiexiuqi <xiexiuqi@huawei.com>, Hanjun Guo <guohanjun@huawei.com>,
        Linux MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH 01/12] mm: add a new config to manage the code
Thread-Topic: [RFC PATCH 01/12] mm: add a new config to manage the code
Thread-Index: AQHQnsY3gIfSqsmrUk2iMAIHCUEUHp2i+t6A///BwsA=
Date: Mon, 8 Jun 2015 15:14:27 +0000
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A8E39B@ORSMSX114.amr.corp.intel.com>
References: <55704A7E.5030507@huawei.com> <55704B0C.1000308@huawei.com>
 <CALq1K=J7BuqMDkPrjioRVyRedHLhmM-gg8MOb9GSBcrmNah23g@mail.gmail.com>
In-Reply-To: <CALq1K=J7BuqMDkPrjioRVyRedHLhmM-gg8MOb9GSBcrmNah23g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by nfs id t58FHAgN022664
Content-Length: 596
Lines: 14

> > +config MEMORY_MIRROR
> > +       bool "Address range mirroring support"
> > +       depends on X86 && NUMA
> > +       default y
> Is it correct for the systems (NOT xeon) without memory support built in?

Is the "&& NUMA" doing that?  If you support NUMA, then you are not a minimal
config for a tablet or laptop.

If you want a symbol that has a stronger correlation to high end Xeon features
then perhaps MEMORY_FAILURE?

-Tony
????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m????????????I?