[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A54299AA4@G01JPEXMBYT01>
Date: Fri, 11 Dec 2015 05:53:17 +0000
From: "Izumi, Taku" <izumi.taku@...fujitsu.com>
To: Xishi Qiu <qiuxishi@...wei.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
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.
>
--
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