Hi Folks, I am working through debugging a bug I am running while trying to run syscall mode in gem5 on the Ruby MOESI_AMD_BASE protocol. To start, the bug I am running into is as follows: src/sim/port.cc:62: fatal: system.cp_cntrl0.memory: Unconnected port!
A few notes to describe what I understand thus far: i. This function is called only during an exception, meaning it was not an in/out port such as the triggerQueue which is not hooked up to a virtual network ii. This doesn't arise when running the example configuration for the ruby_mem_test.py on the MOESI_AMD_BASE protocol iii. In this configuration, modeled closely to parts of the now deprecated se.py, the MESI_two_level protocol runs without issue iv. I have verified that in the MOESI_AMD_BASE.py file, all CorePair in/out ports are connected to the ruby network Because the MESI_two_level protocol runs without issue, I currently believe that there is something I must change or configure in the MOESI_AMD_BASE.py configuration to resolve this issue, but I have not succeeded thus far. Though I don't have all the code here, I can share anything as needed. If anyone has insight, your help is much appreciated! thanks
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
