Messages in this thread | | | Date | Wed, 1 Jun 2022 11:00:23 +0200 | From | David Hildenbrand <> | Subject | Re: [PATCHv6 03/15] efi/x86: Get full memory map in allocate_e820() |
| |
On 17.05.22 17:34, Kirill A. Shutemov wrote: > Currently allocate_e820() only interested in the size of map and size of > memory descriptor to determine how many e820 entries the kernel needs. > > UEFI Specification version 2.9 introduces a new memory type -- > unaccepted memory. To track unaccepted memory kernel needs to allocate > a bitmap. The size of the bitmap is dependent on the maximum physical > address present in the system. A full memory map is required to find > the maximum address. > > Modify allocate_e820() to get a full memory map.
Usually we use max_pfn, if we want to know the maximum pfn that's present in the system (well, IIRC, excluding hotunplug).
How exactly will this (different?) maximum from UEFI for the bitmap interact with
max_pfn = e820__end_of_ram_pfn();
from e820 in existing code
?
-- Thanks,
David / dhildenb
| |