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]

Date:	Fri, 9 Oct 2015 08:08:40 -0700
From:	Dave Hansen <dave.hansen@...el.com>
To:	Xishi Qiu <qiuxishi@...wei.com>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	Taku Izumi <izumi.taku@...fujitsu.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	tony.luck@...el.com, mel@....ul.ie, akpm@...ux-foundation.org,
	Mel Gorman <mgorman@...e.de>, Ingo Molnar <mingo@...nel.org>,
	zhongjiang@...wei.com
Subject: Re: [PATCH][RFC] mm: Introduce kernelcore=reliable option

On 10/09/2015 03:36 AM, Xishi Qiu wrote:
> I mean the mirrored region can not at the middle or end of the zone,
> BIOS should report the memory like this, 
> 
> e.g.
> BIOS
> node0: 0-4G mirrored, 4-8G mirrored, 8-16G non-mirrored
> node1: 16-24G mirrored, 24-32G non-mirrored
> 
> OS
> node0: DMA DMA32 are both mirrored, NORMAL(4-8G), MOVABLE(8-16G)
> node1: NORMAL(16-24G), MOVABLE(24-32G)

I understand if the mirrored regions are always at the start of the zone
today, but is that somehow guaranteed going forward on all future hardware?

I think it's important to at least consider what we would do if DMA32
turned out to be non-reliable.
--
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/