[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALq1K=J8ndi6tfy6nV3BT85bp1FXzxO8+mD9KgBfBpz6ibK7Hg@mail.gmail.com>
Date: Mon, 8 Jun 2015 19:36:01 +0300
From: Leon Romanovsky <leon@...n.nu>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Xishi Qiu <qiuxishi@...wei.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"nao.horiguchi@...il.com" <nao.horiguchi@...il.com>,
Yinghai Lu <yinghai@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
"mingo@...e.hu" <mingo@...e.hu>, Xiexiuqi <xiexiuqi@...wei.com>,
Hanjun Guo <guohanjun@...wei.com>,
Linux MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 01/12] mm: add a new config to manage the code
On Mon, Jun 8, 2015 at 6:14 PM, Luck, Tony <tony.luck@...el.com> wrote:
>> > +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?
I would like to see the default set to be "n".
On my machine (x86_64) defconfig enables this feature and I don't know
if this feature can work there.
➜ linux-mm git:(dev) ✗ make defconfig ARCH=x86
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/bin2c
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
*** Default configuration is based on 'x86_64_defconfig'
#
# configuration written to .config
#
➜ linux-mm git:(dev) ✗ grep CONFIG_MEMORY_MIRROR .config
CONFIG_MEMORY_MIRROR=y
>
> -Tony
--
Leon Romanovsky | Independent Linux Consultant
www.leon.nu | leon@...n.nu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists