Hi, I believe this is because detailed cpu model uses pipeline and other ruby port may be added to the retry list when the previous has not been handled yet. You can refer to function "recvTimingReq" in RubyPort.cc for more informantion.
While in timing model, no pipeline is used and ruby requests are handled one by one, so the makeRequest function always returns Issued. By the way, i am not familiar with real hardware details, so I am not sure what happens in real machines, can anyone explain it? nifan From: Rodrigo Reynolds Ramírez via gem5-users Date: 2014-10-28 01:38 To: gem5-users Subject: [gem5-users] Error with Ruby Hello everyone I am trying to execute the simulator with Ruby model I downloaded it today and I compiled it with this line: scons PROTOCOL=MESI_Three_Level build/X86/gem5.opt -j2 and executed it with this other line: ./build/X86/gem5.opt configs/example/se.py --caches --ruby --cpu-type=detailed -n 2 --cmd="tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello2" when I use timing cpu type all is ok, but with the detailed-cpu type I got this error: gem5 Simulator System. http://gem5.org gem5 is copyrighted software; use the --copyright option for details. gem5 compiled Oct 27 2014 18:32:50 gem5 started Oct 27 2014 18:33:45 gem5 executing on arya command line: ./build/X86/gem5.opt configs/example/se.py --caches --ruby --cpu-type=detailed -n 2 --cmd=tests/test-progs/hello/bin/x86/linux/hello;tests/test-progs/hello/bin/x86/linux/hello2 Global frequency set at 1000000000000 ticks per second 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000 0: system.remote_gdb.listener: listening for remote gdb #1 on port 7001 **** REAL SIMULATION **** info: Entering event queue @ 0. Starting simulation... gem5.opt: build/X86/mem/ruby/system/RubyPort.hh:191: void RubyPort::addToRetryList(RubyPort::MemSlavePort*): Assertion `std::find(retryList.begin(), retryList.end(), port) == retryList.end()' failed. Program aborted at cycle 273000 Aborted (core dumped) I tried with MESI_Two_Level but I got the same error. Thanks in advance Rodrigo
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
