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:10:32 -0500
From:	Paul Jackson <pj@....com>
To:	"Yinghai Lu" <yhlu.kernel@...il.com>
Cc:	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:
> that function seems to increase the ebda to workaround some broken
> machine blindly.

Yes, true.

The reserve_ebda_region() has probably been like that for a while;
do you understand why it would be a problem conflicting with the
EFI memmap only now?

My other two concerns remain as well:

 2) Is what amounts to a change from calling reserve_bootmem()
    to calling reserve_early(), at the end of reserve_ebda_region()
    in the 32 bit case (now that it is merged with the 64 bit code)
    understood to be a desired and correct change?

 3) There has been quite a few patches restructuring this early
    memory reservation code over the last week.  What is the
    state of that work ... is it still "in progress" or is it
    thought to be complete?

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