linux-kernel - RE: [PATCH][RFC] mm: Introduce kernelcore=reliable option

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F32B54CDF@ORSMSX114.amr.corp.intel.com>
Date:	Mon, 12 Oct 2015 18:43:30 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Xishi Qiu <qiuxishi@...wei.com>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Taku Izumi <izumi.taku@...fujitsu.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"mel@....ul.ie" <mel@....ul.ie>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"Hansen, Dave" <dave.hansen@...el.com>,
	Mel Gorman <mgorman@...e.de>, Ingo Molnar <mingo@...nel.org>,
	"zhongjiang@...wei.com" <zhongjiang@...wei.com>,
	"Naoya Horiguchi" <n-horiguchi@...jp.nec.com>,
	Vlastimil Babka <vbabka@...e.cz>,
	Leon Romanovsky <leon@...n.nu>
Subject: RE: [PATCH][RFC] mm: Introduce kernelcore=reliable option

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