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 03:24:57 -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 better to change boot loader to avoid memory area of EBDA.

Would this require the bootloader to know the kernels rather arbitrary
heuristics for inventing and placing an EBDA area, in reserve_ebda_region()?

In general, I would think it better not to have to code into the EFI
firmware or bootloader such knowledge.  But perhaps I am wrong here.

If the kernel is going to reserve an EBDA region even if no EBDA is
requested by the BIOS, then I would think that the kernel should be
more tolerant of BIOS's that put something else in that place.

> Or do not reserve EBDA on EFI system.

I suppose.  This would have been a bigger change than I could
suggest.  For all I know, there are existing systems using EBDA
and EFI together.  Would this change break them?

If you have good reason to know that's essentially impossible then
I have no objections, so far as my needs go, to not reserving EBDA
on EFI systems.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ