I solved that problem also.
This problem is basically related to gem5 versioning. I think after garnet
2.0, Gem5 should publish a new stable version.
This problem is related to below link-
https://gem5-review.googlesource.com/c/2380/
I also obtained the results for simple network with --n 4.
Garnet_standalone is a different dummy protocol which consumes every message so
it'll work. It's not realistic.
Try with other coherence protocols perhaps ...
Cheers,
Tushar
On May 5, 2017, at 2:21 PM, F. A. Faisal
> wrote:
I tried simple
I tried simple network option. However, the result is the same. Please let
me know, if I am missing any option to add (I used all the default
settings).
However, I also run the garent_standalone protocol with the default
settings, which runs properly.
./build/ALPHA/gem5.opt configs/example/fs.py
Hmm the coherence protocol seems to have received an invalid transaction. Not
sure why. This does not seem to be a network issue. But for a sanity check, run
with network=simple and see if it still fails.
Cheers,
Tushar
On May 5, 2017, at 11:46 AM, F. A. Faisal
Thanks a lot.
I already figured out that problem by myself.
However, I encountered a new problem in running 4 core 4 threads
blackscholes benchmarks. It shows system panic.
I also tried for 16 cpu and Mesh network, which is still running more than
8 hours.
I used the mesh_xy topology along with
Hi,
I like to invoke the garnet 2.0 for running the benchmark programs Parsec
2.1.
However, previous ruby_fs.py file located at configs/example/ folder is not
available with the current gem5 source, which could invoke the garnet 1.0.
And now the replaced fs.py file don't have option like-