Hi Nathanael, this is a know problem in develop that will be fixed in next release.
It comes from the fact that we are using 4 table walkers (for S1I-TLB, S1D-TLB, S2I-TLB and S2D-TLB). I am currently working on: a) Implementing a VA indexed walk cache replacing current PWCs (.gem5 _walker_cache) b) Merging table walkers into a single ported object Kind Regards Giacomo > -----Original Message----- > From: Nathanael Premillieu via gem5-users <gem5-users@gem5.org> > Sent: 19 October 2021 12:44 > To: gem5 users mailing list <gem5-users@gem5.org> > Cc: Nathanael Premillieu <nathanael.premill...@huawei.com> > Subject: [gem5-users] Fatal when using ARM config file with walk cache > > Hello, > > > > When using configuration files that define a walk cache > (configs/common/cores/arm/O3_ARM_v7a.py and > configs/common/cores/arm/HPI.py for example), I get the following error: > > > > fatal: Port <orphan System>.cpu.itb_walker_cache.cpu_side is already > connected to <orphan System>.cpu.mmu.itb_walker.port, cannot connect > <orphan System>.cpu.mmu.stage2_itb_walker.port > > > > The command line I use: > > > > $ ./build/ARM/gem5.opt configs/example/se.py --cpu-type O3_ARM_v7a_3 > -c tests/test-progs/hello/bin/arm/linux/hello --caches --l2cache > > > > It seems this problem is due to the connectWalkerPorts function defined in > src/arch/arm/ArmMMU.py, in particular the following two lines (l.100-l.101): > > > > self.stage2_itb_walker.port = iport > > self.stage2_dtb_walker.port = dport > > > > Commenting them out seems to solve the problem, but I'm pretty sure this > is not the correct way of solving it, but I'm not familiar enough with this > code > to find a better one. > > > > Anyone has a better solution? > > > > Thanks, > > Nathanael Premillieu 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 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
