linux-kernel - Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86

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:	Thu, 12 Jun 2008 15:06:32 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Paul Jackson" <pj@....com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, andi@...stfloor.org,
	mingo@...e.hu, bwalle@...e.de, hannes@...urebad.de,
	ying.huang@...el.com, linux-kernel@...r.kernel.org, steiner@....com
Subject: Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86_64

On Thu, Jun 12, 2008 at 2:52 PM, Paul Jackson <pj@....com> wrote:
> hpa writes:
>> It's probably safer to reserve the EBDA even with EFI; it's only a page
>> or so so it doesn't matter much.
>
> Reserving EBDA with EFI is fine by what little I know.
>
> But the current code doesn't like it -- if the EFI memmap range is inside
> the EBDA range, then the reserve_early() routine panics with:
>
>    "Overlapping early reservations"
>
> Something needs tweaking here somehow ... and I'm not the one to know what.

what is addr that the EFI memmap should be according to spec?

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/