Hi,
I download the PARSEC images with pre-compiled benchmark suite from
http://www.cs.utexas.edu/~cart/parsec_m5/
<http://www.cs.utexas.edu/%7Ecart/parsec_m5/>. I extract the
pre-compiled benchmarks into my own disk image made from
util/gem5img.py. According to the document in the above URL, before
entering the ROI, PARSEC will create a checkpoint. So I run the
benchmark (e.g., blackscholes) firstly with configs/common/fs.py as well
as atomic cpu until the checkpoint is generated. Then in second run, I
take configs/common/ruby_fs.py as well as timing cpu and restore from
that checkpoint with detailed measurement of the ROI. However, during my
experiment, I find that when MESI protocol is equipped, gem5 will hang
for many hours after it leaves the ROI. On the other hand, in
MOESI_CMP_directory and MOESI_Hammer cases, the simulation will end as
expected.
Are there any bugs in current MESI protocol implementation to support
Ruby? I am not sure. Wish anyone can give me some suggestions.
Many thanks,
Hanfeng
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
