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 17:13:54 -0500
From:	Paul Jackson <pj@....com>
To:	"Yinghai Lu" <yhlu.kernel@...il.com>
Cc:	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

Yinghai wrote:
> what is addr that the EFI memmap should be according to spec?

The EFI memmap has no specific address by specification.  Rather the
BIOS/firmware can put it where it will, and then pass that address via
the boot_parms.efi_info.memmap field.  See include/asm-x86/bootparam.h
for these structures.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/