Hi On 8/2/22 22:46, larried1...@gmail.com wrote:
Hi Giacomo, Where can I control the bootloader? In my config file I basically just follow the example FSConfig.py to setup the bootloader: https://github.com/gem5/gem5/blob/1d03f6de941520860c673b5f7954c82a46e8b191/configs/common/FSConfig.py#L295 Do I need to modify the bootloader file to make it work?
You definitely don't need to modify the bootloader. There is probably something wrong in the way you have connected you platform in the python world (it is a routing issue). The bootloader should be loaded in the bootmem memory (see src/dev/arm/RealView.py) based on its starting address. And as far as you told me bootmem is connected to membus0. This leads me to believe the failing fetch request starts from a cpu in the second NUMA node (this can be easily verified via GDB). When the fetch reaches the membus1, it is not able to be routed to bootmem as it is not directly connected to the bus. It should go through numa_caches_downward1 -> system_bus -> etc, but from your config.ini I see the numa_caches_downward is configured with DRAM only address ranges. It should include the bootmem range as well in order to accept memory requests falling in that range... This should fix the issue I believe. Kind Regards Giacomo
_______________________________________________ gem5-users mailing list --gem5-users@gem5.org To unsubscribe send an email togem5-users-le...@gem5.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
