efi_loader: fix memory allocation on sandbox
Commit7b78d6438a
("efi_loader: Reserve unaccessible memory") introduced a comparison between RAM top and RAM start that was not known at the time when the patch of commit49759743bf
("efi_loader: eliminate sandbox addresses") was written. The sandbox uses an address space that is only relevant in the sandbox context. We have to map ram_top from the sandbox address space to the physical address space before using it in the EFI subsystem. Fixes:49759743bf
("efi_loader: eliminate sandbox addresses") Fixes:7b78d6438a
("efi_loader: Reserve unaccessible memory") Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Alexander Graf <agraf@suse.de>
This commit is contained in:
parent
0ea8741ff6
commit
23f5f4abf7
@ -554,6 +554,12 @@ __weak void efi_add_known_memory(void)
|
||||
u64 ram_top = board_get_usable_ram_top(0) & ~EFI_PAGE_MASK;
|
||||
int i;
|
||||
|
||||
/*
|
||||
* ram_top is just outside mapped memory. So use an offset of one for
|
||||
* mapping the sandbox address.
|
||||
*/
|
||||
ram_top = (uintptr_t)map_sysmem(ram_top - 1, 0) + 1;
|
||||
|
||||
/* Fix for 32bit targets with ram_top at 4G */
|
||||
if (!ram_top)
|
||||
ram_top = 0x100000000ULL;
|
||||
|
Loading…
Reference in New Issue
Block a user