[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <566A9AE1.7020001@huawei.com>
Date: Fri, 11 Dec 2015 17:44:01 +0800
From: Xishi Qiu <qiuxishi@...wei.com>
To: "Izumi, Taku" <izumi.taku@...fujitsu.com>
CC: "Luck, Tony" <tony.luck@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>,
"mel@....ul.ie" <mel@....ul.ie>,
"Hansen, Dave" <dave.hansen@...el.com>,
"matt@...eblueprint.co.uk" <matt@...eblueprint.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,
I mean when zone_movable is from kernelcore=mirror, not kernelcore=nn[KMG].
Thanks,
Xishi Qiu
> 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.
>>
>
> --
> 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/
>
> .
>
--
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