On Mon, 22 Apr 2013, Marco Elver wrote:
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1829/#review4272
-----------------------------------------------------------
Thanks, Nilay! With the "flexible" pipeline model I have successfully run one
benchmark to completion.
However, there still appear to be problems with the "fixed" pipeline:
gem5 Simulator System. http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.
gem5 compiled Apr 22 2013 16:30:35
gem5 started Apr 22 2013 18:10:47
gem5 executing on arch
command line: ./build/X86_MESI_CMP_directory/gem5.opt
configs/example/ruby_fs.py -n 32 --cpu-type timing --mem-size 2048MB --kernel
system/x86_64-vmlinux-2.6.32.60.smp --l1d_size 32kB --l1d_assoc 4 --l1i_size
32kB --l1i_assoc 4 --l2_size 1024kB --l2_assoc 16 --num-l3caches 0
--num-l2caches 32 --num-dirs 32 --topology Mesh --mesh-rows 4 --checkpoint-dir
new-cpt/output/MOESI_hammer,32timing-stamp,genome/checkpoints -r 0
--restore-with-cpu timing --garnet-network fixed
warn: add_child('terminal'): child 'terminal' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
<line above repeated 148 times>
Global frequency set at 1000000000000 ticks per second
info: kernel located at:
/home/marco/gem5/system/binaries/system/x86_64-vmlinux-2.6.32.60.smp
0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012
Listening for com_1 connection on port 3457
warn: Reading current count from inactive timer.
**** REAL SIMULATION ****
info: Entering event queue @ 0. Starting simulation...
info: Entering event queue @ 5512909158000. Starting simulation...
panic: Possible Deadlock detected. Aborting!
version: 2 request.paddr: 0x[0x7e623000, line 0x7e623000] m_readRequestTable: 1
current time: 5513159158000 issue_time: 5512909158000 difference: 250000000
@ cycle 2756260
[wakeup:build/X86_MESI_CMP_directory/mem/ruby/system/Sequencer.cc, line 107]
Memory Usage: 2756260 KBytes
Program aborted at cycle 5513159158000
Note that the point at which gem5 re-enters the event queue is the same as the
issue time of the request which triggered the deadlock (5512909158000).
Apply the following patch and report what happens with fixed-pipeline run
you mentioned above.
diff --git a/src/mem/ruby/system/System.cc b/src/mem/ruby/system/System.cc
--- a/src/mem/ruby/system/System.cc
+++ b/src/mem/ruby/system/System.cc
@@ -381,6 +381,7 @@
// Restore eventq head
eventq_head = eventq->replaceHead(eventq_head);
// Restore curTick and Ruby System's clock
+ assert(curTick() <= curtick_original);
setCurTick(curtick_original);
resetClock();
}
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
