Alexander Graf 5d00995c36 efi_loader: Implement memory allocation and map ... The EFI loader needs to maintain views of memory - general system memory windows as well as used locations inside those and potential runtime service MMIO windows. To manage all of these, add a few helpers that maintain an internal representation of the map the similar to how the EFI API later on reports it to the application. For allocations, the scheme is very simple. We basically allow allocations to replace chunks of previously done maps, so that a new LOADER_DATA allocation for example can remove a piece of the RAM map. When no specific address is given, we just take the highest possible address in the lowest RAM map that fits the allocation size. Signed-off-by: Alexander Graf <agraf@suse.de> Tested-by: Simon Glass <sjg@chromium.org>		2016-03-15 21:30:10 -04:00
..
efi_boottime.c	efi_loader: Add runtime services	2016-03-15 18:03:10 -04:00
efi_console.c	efi_loader: Add console interface	2016-03-15 18:03:09 -04:00
efi_disk.c	efi_loader: Add disk interfaces	2016-03-15 18:03:11 -04:00
efi_image_loader.c	efi_loader: Add PE image loader	2016-03-15 15:19:23 -04:00
efi_memory.c	efi_loader: Implement memory allocation and map	2016-03-15 21:30:10 -04:00
efi_runtime.c	efi_loader: Add runtime services	2016-03-15 18:03:10 -04:00