linux-kernel - Re: [PATCH] x86: extend e820 ealy_res support 32bit

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: <86802c440805291141i7fdc73e8p56e4728996337abc@mail.gmail.com>
Date:	Thu, 29 May 2008 11:41:54 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Jeremy Fitzhardinge" <jeremy@...p.org>
Cc:	"Rusty Russell" <rusty@...tcorp.com.au>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Ingo Molnar" <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: extend e820 ealy_res support 32bit - fix #2

On Thu, May 29, 2008 at 6:37 AM, Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> Yinghai Lu wrote:
>>
>> can we use e820 entries for that? So the domain builder could have
>> several entries for E820_RAM and E820_RESERVED...
>>
>
> I tried this, but it doesn't work; the kernel crashes during boot,
> presumably because it's trying to use the reserved memory as heap.  I
> suspect the e820 maps are not registered early enough or something...
>
> (One thought: if reserving in the E820 map were enough, then couldn't we use
> it for all the early reservations?)

"e820 reserved entries" means kernel will only read it.

reserve_early will be converted to bootmem via reserve_bootmem[_generic]
and later it could be freed and be reused.

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