u-boot.git/lib/efi_loader/efi_memory.c, branch v2019.07

efi_loader: AllocatePages() must accept addr == 0

2019-06-14T17:18:40+00:00

It must be possible to allocate memory at address 0 with AllocatePages().

Move a NULL pointer check.

Signed-off-by: Heinrich Schuchardt

efi_loader: event signaling in ExitBootServices

2019-06-10T21:06:19+00:00

ExitBootServices() has to stop timer related activity before calling the
events of the EFI_EVENT_GROUP_EXIT_BOOT_SERVICES event group. But our
current implementation was stopping all other events.

All events have to observe the task priority level.

Signed-off-by: Heinrich Schuchardt

efi_loader: notify memory map changes

2019-06-04T20:09:38+00:00

When the memory map is changed signal events of the
EFI_EVENT_GROUP_MEMORY_MAP_CHANGE event group.

Signed-off-by: Heinrich Schuchardt

efi_loader: simplify efi_allocate_pages()

2019-05-12T18:54:22+00:00

Replace unnecessary control structures by using return statements.

Signed-off-by: Heinrich Schuchardt

efi_loader: AllocateAdress error handling

2019-05-12T18:54:22+00:00

If AllocatePages() is called with AllocateAddress, the UEFI spec requires
to return EFI_NOT_FOUND in case the memory page does not exist.

The UEFI SCT II 2017 spec additionally requires to return EFI_NOT_FOUND if
the page is already allocated.

Check that *Memory refers to an unallocated page.

UEFI SCT II (2017): AllocatePages(), 5.1.2.1.9 - 5.1.2.1.10

Signed-off-by: Heinrich Schuchardt

efi_loader: out of resources in AllocatePages()

2019-05-12T18:54:22+00:00

According to the UEFI AllocatePages() has to return EFI_OUT_OF_RESOURCES if
sufficient memory is not available.

Change the return value.

UEFI SCT II (2017): 3.2.1 AllocatePages(), 5.1.2.1.8

Signed-off-by: Heinrich Schuchardt

efi_loader: check memory address before freeing

2019-05-12T18:54:22+00:00

When we call FreePages() we essentially add memory to our memory map. We
shouldn't do this for memory that does not exit.

Check if the memory that is to be freed via FreePages() or FreePool() is in
our memory map and is not EFI_CONVENTIONAL_MEMORY.

This check is mandated by the UEFI specification.

Cf. UEFI SCT  II (2017), 3.2.2 FreePages(), 5.1.2.1 - 5.1.2.2

Signed-off-by: Heinrich Schuchardt

efi_loader: FreePages() must fail with pages = 0

2019-05-02T16:17:49+00:00

The UEFI spec requires that freeing of pages fails if the number of pages
to be freed is 'invalid'. Check that it is not zero.

Signed-off-by: Heinrich Schuchardt

efi_loader: check memory type in AllocatePages()

2019-04-22T22:37:28+00:00

The UEFI specification prescribes that AllocatePages() checks the memory
type.

Signed-off-by: Heinrich Schuchardt

efi_loader: update virtual address in efi_mem_carve_out

2019-04-12T20:00:42+00:00

Handle virtual address in efi_mem_carve_out() function
when a new region is created to avoid issue in EFI memory map.

Signed-off-by: Patrick Delaunay 

At boottime physical and virtual addressed have to be the same.
This allowed to simplify the proposed logic.

Reviewed-by: Heinrich Schuchardt