linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Taku Izumi <izumi.taku@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"mel@csn.ul.ie" <mel@csn.ul.ie>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"Hansen, Dave" <dave.hansen@intel.com>,
	Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@kernel.org>,
	"zhongjiang@huawei.com" <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: Mon, 12 Oct 2015 18:43:30 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32B54CDF@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <56187188.4070103@huawei.com>

> 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?

Exact methods may vary as different BIOS vendors implement things the way
they like (or the way an OEM asks them).  In the Intel reference BIOS you can either
set an explicit mirror size for each memory controller, or you can have the BIOS
look at some EFI boot variables to find a percentage of memory to use spread
across all memory controllers.

See:
https://software.intel.com/sites/default/files/managed/43/6a/Memory%20Address%20Range%20Mirroring%20Validation%20Guide.pdf

There are patches to efibootmgr(8) to set/show the EFI variables:
git://github.com/rhinstaller/efibootmgr

-Tony
 



--
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>

  reply	other threads:[~2015-10-12 18:43 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
2015-10-12 18:43         ` Luck, Tony [this message]
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=3908561D78D1C84285E8C5FCA982C28F32B54CDF@ORSMSX114.amr.corp.intel.com \
    --to=tony.luck@intel.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=qiuxishi@huawei.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