Hi:
I believe there is a bug in MESI_Three_Level.py.
when I tried to run build/MESI_Three_Level/gem5.debug config/example/fs.py
--ruby
I got a segment fault, I track the code and found it occurs in the initfunction
in DMA_Controller.cc, after careful comparision with MESI_Two_Level. I modified
ruby/mesi_three_level.py as follows,
the original code :
215 exec("ruby_system.dma_cntrl%d = dma_cntrl" % i)
216 exec("ruby_system.dma_cntrl%d.dma_sequencer.slave = dma_port" %
i)
217 dma_cntrl_nodes.append(dma_cntrl)
218
219 all_cntrls = l0_cntrl_nodes + \
Two lines are added as marked red.
194 exec("ruby_system.dma_cntrl%d = dma_cntrl" % i)
195 dma_cntrl_nodes.append(dma_cntrl)
196
197 # Connect the dma controller to the network
198 dma_cntrl.responseFromDir = ruby_system.network.master
199 dma_cntrl.requestToDir = ruby_system.network.slave
200
201 all_cntrls = l1_cntrl_nodes + \
After the modification, every thing goes fine.
IS it a real bug or it happens just because I missed something?
can anyone confirm it, thanks a lot.
-----------
>From Tommy
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
