aboutsummaryrefslogtreecommitdiff
path: root/lib/vsprintf.c
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2018-06-18 17:23:15 +0200
committerAlexander Graf <agraf@suse.de>2018-07-25 14:57:44 +0200
commit282a06cbcae84acd86125210dbd54a10ff41e809 (patch)
tree5b29af4cdcef7080b1238e79160b29e5b888d0c4 /lib/vsprintf.c
parent69259b83670661ad530442e1ebb788e96a7676cb (diff)
downloadu-boot-282a06cbcae84acd86125210dbd54a10ff41e809.zip
u-boot-282a06cbcae84acd86125210dbd54a10ff41e809.tar.gz
u-boot-282a06cbcae84acd86125210dbd54a10ff41e809.tar.bz2
efi_loader: Expose U-Boot addresses in memory map for sandbox
We currently expose host addresses in the EFI memory map. That can be bad if we ever want to use sandbox to boot strap a real kernel, because then the kernel would fetch its memory table from our host virtual address map. But to make that use case work, we would need to have full control over the address space the EFI application sees. So let's expose only U-Boot addresses to the guest until we get to the point of allocation. EFI's allocation functions are fun - they can take U-Boot addresses as input values for hints and return host addresses as allocation results through the same uint64_t * parameter. So we need to be extra careful on what to pass in when. With this patch I am successfully able to run the efi selftest suite as well as grub.efi on aarch64. Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'lib/vsprintf.c')
0 files changed, 0 insertions, 0 deletions