Hi Alex, On 18 June 2018 at 09:23, Alexander Graf <ag...@suse.de> wrote: > 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 <ag...@suse.de> > --- > arch/sandbox/cpu/cpu.c | 19 ------------------- > lib/efi_loader/efi_memory.c | 12 ++++++------ > 2 files changed, 6 insertions(+), 25 deletions(-)
Can you please point me to your latest series? I think you have decided to work on this yourself and pick bits from my series that you like. This I consider unpleasant behaviour for a maintainer, but ultimately I'm more interested in getting things resolved than any procedural issues. Please don't do this to anyone else, though, in the U-Boot community. Anyway, at present I'm not sure what state it is in, so please point me to your latest tree so I can take a look and figure out what has actually changed from my v9 series. Regards, Simon Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
