linux-kernel - Re: [PATCH 4/8] x86 boot: allow overlapping ebda and efi memmap memory ranges

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:	Mon, 16 Jun 2008 04:09:04 -0500
From:	Paul Jackson <pj@....com>
To:	"Huang, Ying" <ying.huang@...el.com>
Cc:	mingo@...e.hu, tglx@...utronix.de, yhlu.kernel@...il.com,
	steiner@....com, travis@....com, hpa@...or.com,
	linux-kernel@...r.kernel.org, andi@...stfloor.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 4/8] x86 boot: allow overlapping ebda and efi memmap
 memory ranges

Huang wrote:
> I think it is sufficient for boot loader to avoid memory area from
> 0x9f000 to 0x100000. This can be seen as compatible code for legacy
> BIOS.

That might work -- I'll give it a try.

> I think if EBDA area is used in EFI system, it should be reserved in EFI
> memory map.

Would you recommend doing this with code in arch/x86/kernel/head.c,
that did not invoke reserve_ebda_region() if efi_enabled was set?

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