From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
CC: Andrew Morton <akpm@linux-foundation.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Xiexiuqi <xiexiuqi@huawei.com>, Linux MM <linux-mm@kvack.org>
Subject: RE: [RFC 0/3] Mirrored memory support for boot time allocations
Thread-Topic: [RFC 0/3] Mirrored memory support for boot time allocations
Thread-Index: AQHQkUC5JSuQv5ZyJEiJ0ubTXY/x252B/9iQ
Date: Mon, 18 May 2015 17:42:42 +0000
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A86CBC@ORSMSX114.amr.corp.intel.com>
References: <cover.1423259664.git.tony.luck@intel.com>
 <55599BAA.20204@huawei.com>
In-Reply-To: <55599BAA.20204@huawei.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 877
Lines: 21

> Is it means that you will create a new zone to fill mirrored memory, like the
> movable zone, right? 

That's my general plan.

> I think this will change a lot of code, why not create a new migrate type?
> such as CMA, e.g. MIGRATE_MIRROR

I'm still exploring options ... the idea is to use mirrored memory for kernel allocations
(because our machine check recovery code will always crash the system for errors
in kernel memory - while we can avoid the crash for errors in application memory).
I'm not familiar with CMA ... can you explain a bit how it might let me direct kernel
allocations to specific areas of memory?

-Tony

--
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/