From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752213AbbLKFx0 (ORCPT ); Fri, 11 Dec 2015 00:53:26 -0500 Received: from mgwym03.jp.fujitsu.com ([211.128.242.42]:40124 "EHLO mgwym03.jp.fujitsu.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751216AbbLKFxZ (ORCPT ); Fri, 11 Dec 2015 00:53:25 -0500 From: "Izumi, Taku" To: Xishi Qiu CC: "Luck, Tony" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "akpm@linux-foundation.org" , "Kamezawa, Hiroyuki" , "mel@csn.ul.ie" , "Hansen, Dave" , "matt@codeblueprint.co.uk" Subject: RE: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option Thread-Topic: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option Thread-Index: AQHRMjAR2Z6g1ySguUa1IzGGIcYfOZ7BaBYAgAE2XICAADaQAIAAt+Yw//+bsYCAAh8zoA== Date: Fri, 11 Dec 2015 05:53:17 +0000 Message-ID: References: <1449631109-14756-1-git-send-email-izumi.taku@jp.fujitsu.com> <1449631177-14863-1-git-send-email-izumi.taku@jp.fujitsu.com> <56679FDC.1080800@huawei.com> <3908561D78D1C84285E8C5FCA982C28F39F7F4CD@ORSMSX114.amr.corp.intel.com> <5668D1FA.4050108@huawei.com> <56691819.3040105@huawei.com> In-Reply-To: <56691819.3040105@huawei.com> Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-securitypolicycheck: OK by SHieldMailChecker v2.3.2 x-shieldmailcheckerpolicyversion: FJ-ISEC-20150624-1 x-shieldmailcheckermailid: 8b4869f422594318a7275a406d74f356 x-originating-ip: [10.124.102.50] Content-Type: text/plain; charset="iso-2022-jp" MIME-Version: 1.0 X-SecurityPolicyCheck-GC: OK by FENCE-Mail X-TM-AS-MML: disable Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Xishi, > Hi Taku, > > Whether it is possible that we rewrite the fallback function in buddy system > when zone_movable and mirrored_kernelcore are both enabled? What does "when zone_movable and mirrored_kernelcore are both enabled?" mean ? My patchset just provides a new way to create ZONE_MOVABLE. Sincerely, Taku Izumi > > It seems something like that we add a new zone but the name is zone_movable, > not zone_mirror. And the prerequisite is that we won't enable these two > features(movable memory and mirrored memory) at the same time. Thus we can > reuse the code of movable zone. >