From: Xishi Qiu <qiuxishi@huawei.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
tony.luck@intel.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, mel@csn.ul.ie,
akpm@linux-foundation.org, Dave Hansen <dave.hansen@intel.com>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>,
zhongjiang@huawei.com,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Vlastimil Babka <vbabka@suse.cz>, Leon Romanovsky <leon@leon.nu>
Subject: Re: [PATCH][RFC] mm: Introduce kernelcore=reliable option
Date: Sat, 10 Oct 2015 10:01:44 +0800 [thread overview]
Message-ID: <56187188.4070103@huawei.com> (raw)
In-Reply-To: <5617989E.9070700@huawei.com>
On 2015/10/9 18:36, Xishi Qiu wrote:
> On 2015/10/9 17:24, Kamezawa Hiroyuki wrote:
>
>> On 2015/10/09 15:46, Xishi Qiu wrote:
>>> On 2015/10/9 22:56, Taku Izumi wrote:
>>>
>>>> Xeon E7 v3 based systems supports Address Range Mirroring
>>>> and UEFI BIOS complied with UEFI spec 2.5 can notify which
>>>> ranges are reliable (mirrored) via EFI memory map.
>>>> Now Linux kernel utilize its information and allocates
>>>> boot time memory from reliable region.
>>>>
>>>> My requirement is:
>>>> - allocate kernel memory from reliable region
>>>> - allocate user memory from non-reliable region
>>>>
>>>> In order to meet my requirement, ZONE_MOVABLE is useful.
>>>> By arranging non-reliable range into ZONE_MOVABLE,
>>>> reliable memory is only used for kernel allocations.
>>>>
Hi,
If we reuse the movable zone, we should set appropriate size of
mirrored memory region(normal zone) and non-mirrored memory
region(movable zone). In some cases, kernel will take more memory
than user, e.g. some apps run in kernel space, like module.
I think user can set the size in BIOS interface, right?
Thanks,
Xishi Qiu
--
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-10-10 2:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 14:56 Taku Izumi
2015-10-09 6:46 ` Xishi Qiu
2015-10-09 9:24 ` Kamezawa Hiroyuki
2015-10-09 10:36 ` Xishi Qiu
2015-10-09 15:08 ` Dave Hansen
2015-10-09 18:51 ` Luck, Tony
2015-10-12 10:32 ` Matt Fleming
2015-10-10 2:01 ` Xishi Qiu [this message]
2015-10-12 18:43 ` Luck, Tony
2015-10-13 9:51 ` Kamezawa Hiroyuki
2015-10-09 21:43 ` Luck, Tony
2015-10-14 1:19 ` Izumi, Taku
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=56187188.4070103@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=leon@leon.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=zhongjiang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox