Hi Sampad, I don't know the answer to this question directly, but I'm CC'ing the AMD folks who hopefully can provide the answer. I mentioned this to Matt P earlier and he thinks it may be a bug.
Thanks, Matt On Fri, Jul 31, 2020 at 10:47 AM Sampad Mohapatra via gem5-dev < [email protected]> wrote: > Hi All, > > I have two queries related to apu_se.py. > > (1) > In both AMD staging and public/develop, apu_se.py has two unused variables: > > hsapp_gpu_map_vaddr = 0x200000000 > hsapp_gpu_map_size = 0x1000 > > Are they unnecessary or should they actually be used somewhere ? > > (2) > The following is passed as pioAddr to the HSAPacketProcessor. > hsapp_gpu_map_paddr = int(Addr(options.mem_size)) > > And then the following assignment is done. > # Map workload to this address space > host_cpu.workload[0].map(0x10000000, 0x200000000, 4096) > > Should the physical address to the workload map be the same as pioAddr of > HSAPacketProcessor, i.e. greater than physical memory size and should the > virtual address of the workload map remain 0x10000000 ? > > As a whole, are the above mentioned variables related ? If yes, then how ? > Are some of them accidentally hardcoded and should actually be variables? > Please advise. > > Thank you, > Sampad > _______________________________________________ > gem5-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
