efi_loader: EFI_PRINT instead of debug for memory services
For debug messages inside EFI API functions we should use the EFI_PRINT macro which gives us well aligned output like: EFI: Entry efi_allocate_pool_ext(4, 14, 000000007edd7718) EFI: efi_add_memory_map: 0x7dcfa000 0x1 4 yes EFI: Exit: efi_allocate_pool_ext: 0 Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
This commit is contained in:
parent
cc2ed79182
commit
e301e024e5
@ -229,8 +229,8 @@ uint64_t efi_add_memory_map(uint64_t start, uint64_t pages, int memory_type,
|
||||
bool carve_again;
|
||||
uint64_t carved_pages = 0;
|
||||
|
||||
debug("%s: 0x%llx 0x%llx %d %s\n", __func__,
|
||||
start, pages, memory_type, overlap_only_ram ? "yes" : "no");
|
||||
EFI_PRINT("%s: 0x%llx 0x%llx %d %s\n", __func__,
|
||||
start, pages, memory_type, overlap_only_ram ? "yes" : "no");
|
||||
|
||||
if (memory_type >= EFI_MAX_MEMORY_TYPE)
|
||||
return EFI_INVALID_PARAMETER;
|
||||
|
Loading…
Reference in New Issue
Block a user