- edk2 memory map on QEMU
Re: edk2 memory map on QEMU
I am playing around with EDK2 on QEMU with a UEFI shell application
and in the app I allocate some memory using
Programmatically accessing the pointer returned works fine, but when
I print it, it does not seem to be what I would expect is a valid
I've allocated 4GB to the QEMU machine, which I believe starts at
You can run the `memmap` command at the EFI Shell to see the layout.
But, when I print the address returned by AllocatePool the value is
Print != printf on some of the format string so be careful about that….
I thought that all memory was identity mapped where phys=virt, so
not sure where the 0x39177018 is coming from. Trying to dump
0x39177018 from the QEMU console or GDB results in a bad address
Join firstname.lastname@example.org to automatically receive all group messages.