From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752779AbbLQEzT (ORCPT ); Wed, 16 Dec 2015 23:55:19 -0500 Received: from szxga03-in.huawei.com ([119.145.14.66]:61192 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751356AbbLQEzS (ORCPT ); Wed, 16 Dec 2015 23:55:18 -0500 Message-ID: <56723E8B.8050201@huawei.com> Date: Thu, 17 Dec 2015 12:48:11 +0800 From: Xishi Qiu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Kamezawa Hiroyuki CC: "Izumi, Taku" , "Luck, Tony" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "akpm@linux-foundation.org" , "mel@csn.ul.ie" , "Hansen, Dave" , "matt@codeblueprint.co.uk" Subject: Re: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option 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> <566A9AE1.7020001@huawei.com> <56722258.6030800@huawei.com> <567223A7.9090407@jp.fujitsu.com> In-Reply-To: <567223A7.9090407@jp.fujitsu.com> Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.25.179] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.56723E96.008B,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: b2b35bec5b8fcc2af76fc6409ea5a59c Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2015/12/17 10:53, Kamezawa Hiroyuki wrote: > On 2015/12/17 11:47, Xishi Qiu wrote: >> On 2015/12/17 9:38, Izumi, Taku wrote: >> >>> Dear Xishi, >>> >>> Sorry for late. >>> >>>> -----Original Message----- >>>> From: Xishi Qiu [mailto:qiuxishi@huawei.com] >>>> Sent: Friday, December 11, 2015 6:44 PM >>>> To: Izumi, Taku/泉 拓 >>>> 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 >>>> >>>> On 2015/12/11 13:53, Izumi, Taku wrote: >>>> >>>>> 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. >>>>> >>>> >>>> Hi Taku, >>>> >> >> Hi Taku, >> >> We can NOT specify kernelcore= "nn[KMG]" and "mirror" at the same time. >> So when we use "mirror", in fact, the movable zone is a new zone. I think it is >> more appropriate with this name "mirrored zone", and also we can rewrite the >> fallback function in buddy system in this case. > > kernelcore ="mirrored zone" ? No, it's zone_names[MAX_NR_ZONES] How about "Movable", -> "Non-mirrored"? > > BTW, let me confirm. > > ZONE_NORMAL = mirrored > ZONE_MOVABLE = not mirrored. > Yes, > so, the new zone is "not-mirrored" zone. > > Now, fallback function is > > movable -> normal -> DMA. > > As Tony requested, we may need a knob to stop a fallback in "movable->normal", later. > If the mirrored memory is small and the other is large, I think we can both enable "non-mirrored -> normal" and "normal -> non-mirrored". Thanks, Xishi Qiu > Thanks, > -Kame > > > > > > > > . >