linux-kernel - Re: [RFC v2 0/2] Early use of boot service memory

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: <20131121233831.GB32121@srcf.ucam.org>
Date:	Thu, 21 Nov 2013 23:38:31 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	jerry.hoemann@...com
Cc:	rob@...dley.net, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, x86@...nel.org, matt.fleming@...el.com,
	yinghai@...nel.org, akpm@...ux-foundation.org, bp@...e.de,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-efi@...r.kernel.org, penberg@...nel.org,
	mingo.kernel.org@...il.com, vgoyal@...hat.com
Subject: Re: [RFC v2 0/2] Early use of boot service memory

On Thu, Nov 21, 2013 at 04:31:04PM -0700, jerry.hoemann@...com wrote:

> I tried this back on 3.11 kernel and reserve_crashkernel after free of
> boot services failed.  I will admit to not digging in too deeply as to
> why it failed.

Hm. If the problem is fragmentation, then yeah, I can imagine this 
causing problems. In that case we could take a two-pass approach - find 
a gap that *will* be big enough, reserve everything that isn't currently 
reserved, and then reserve the rest after ExitBootServices()?

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/