From: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"Hansen, Dave" <dave.hansen@intel.com>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: RE: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option
Date: Fri, 11 Dec 2015 05:53:17 +0000 [thread overview]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A54299AA4@G01JPEXMBYT01> (raw)
In-Reply-To: <56691819.3040105@huawei.com>
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.
>
WARNING: multiple messages have this Message-ID (diff)
From: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"Hansen, Dave" <dave.hansen@intel.com>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: RE: [PATCH v3 2/2] mm: Introduce kernelcore=mirror option
Date: Fri, 11 Dec 2015 05:53:17 +0000 [thread overview]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A54299AA4@G01JPEXMBYT01> (raw)
In-Reply-To: <56691819.3040105@huawei.com>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-12-11 5:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 3:18 [PATCH v3 0/2] mm: Introduce kernelcore=mirror option Taku Izumi
2015-12-09 3:18 ` Taku Izumi
2015-12-09 3:19 ` [PATCH v3 1/2] mm: Calculate zone_start_pfn at zone_spanned_pages_in_node() Taku Izumi
2015-12-09 3:19 ` Taku Izumi
2015-12-09 3:19 ` [PATCH v3 2/2] mm: Introduce kernelcore=mirror option Taku Izumi
2015-12-09 3:19 ` Taku Izumi
2015-12-09 3:28 ` Xishi Qiu
2015-12-09 3:28 ` Xishi Qiu
2015-12-09 21:59 ` Luck, Tony
2015-12-09 21:59 ` Luck, Tony
2015-12-10 1:14 ` Xishi Qiu
2015-12-10 1:14 ` Xishi Qiu
2015-12-10 5:37 ` Izumi, Taku
2015-12-10 5:37 ` Izumi, Taku
2015-12-10 6:13 ` Xishi Qiu
2015-12-10 6:13 ` Xishi Qiu
2015-12-11 5:53 ` Izumi, Taku [this message]
2015-12-11 5:53 ` Izumi, Taku
2015-12-11 9:44 ` Xishi Qiu
2015-12-11 9:44 ` Xishi Qiu
2015-12-17 1:38 ` Izumi, Taku
2015-12-17 1:38 ` Izumi, Taku
2015-12-17 2:47 ` Xishi Qiu
2015-12-17 2:47 ` Xishi Qiu
2015-12-17 2:53 ` Kamezawa Hiroyuki
2015-12-17 2:53 ` Kamezawa Hiroyuki
2015-12-17 4:48 ` Xishi Qiu
2015-12-17 4:48 ` Xishi Qiu
2015-12-17 5:01 ` Kamezawa Hiroyuki
2015-12-17 5:01 ` Kamezawa Hiroyuki
2015-12-17 18:43 ` Luck, Tony
2015-12-17 18:43 ` Luck, Tony
2015-12-18 2:12 ` Kamezawa Hiroyuki
2015-12-18 2:12 ` Kamezawa Hiroyuki
2015-12-18 6:59 ` Luck, Tony
2015-12-18 6:59 ` Luck, Tony
2015-12-28 22:21 ` Andrew Morton
2015-12-28 22:21 ` Andrew Morton
2015-12-28 22:32 ` Andrew Morton
2015-12-28 22:32 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E86EADE93E2D054CBCD4E708C38D364A54299AA4@G01JPEXMBYT01 \
--to=izumi.taku@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt@codeblueprint.co.uk \
--cc=mel@csn.ul.ie \
--cc=qiuxishi@huawei.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.