[edk2-devel] edk2 memory map on QEMU

[Andrew Fish via groups.io]

> On Jul 30, 2021, at 12:32 PM, Stuart Yoder <stuart.yoder at arm.com> wrote:
> 
> I am playing around with EDK2 on QEMU with a UEFI shell application and in the app I allocate some memory using gBS->AllocatePool(EfiBootServicesData, ...)
> 
> 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 address.
> 
> I've allocated 4GB to the QEMU machine, which I believe starts at 0x40000000.
> 

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 "0x39177018".
> 

Print != printf on some of the format string so be careful about that….

Thanks,

Andrew Fish

> 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 error.
> Thanks,
> Stuart
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#78457): https://edk2.groups.io/g/devel/message/78457
Mute This Topic: https://groups.io/mt/84558767/1813853
Group Owner: devel+owner at edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [edk2-devel-archive at redhat.com]
-=-=-=-=-=-=-=-=-=-=-=-


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/edk2-devel-archive/attachments/20210730/f3ce081e/attachment.htm>