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 19:53:40 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Paul Jackson <pj@....com>, Yinghai Lu <yhlu.kernel@...il.com>,
	ying.huang@...el.com, mingo@...e.hu, tglx@...utronix.de,
	steiner@....com, travis@....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

On Mon, 16 Jun 2008 11:18:12 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> Paul Jackson wrote:
> > Yinghai wrote:
> >> like to see to make reserve_ebda_region() more smart like the old
> >> way when andi introduced ebda_size... instead of reserve 0x9000 to
> >> 0x100000 all the way.
> > 
> > Looking back at some older kernels, that code seems to have setup an
> > ebda region only if there was a non-zero real mode pointer at 0x40E.
> > 
> > This is rather different than always setting up such a region.
> > 
> 
> Well, sort of.  Only some very old systems will not have had one.
> 
> 0x40E contains the pointer to the EBDA; this basically tests for the 
> existence of an EBDA at all.

I'd disagree with the "very old". Machines without EBDA go right up to
the AMD Athlon era and maybe beyond that. My old dual Athlon box has no
EBDA.

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