Re: [gem5-users] FS simulation with Garnet 2.0

[F. A. Faisal]

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. However, I run
the simulation for more than 24 hours with 16 cores and still the program
is running!!!
Whereas, --n 4 with same benchmark simulation took around 2 hours to
complete. Please let me know if I am missing something.

Other than below options, rest of the options are default-

/build/ALPHA/gem5.opt configs/example/fs.py --cpu-type=timing
--script=script/blackscholes_4c_simsmall.rcS --num-cpus=16 --ruby
--mesh-rows=4 --network=garnet2.0 --topology=Mesh_XY --caches --l2cache
--l2_size=256MB --num-dirs=16 --num-l2=16 --l1d_size=32kB --l1i_size=32kB
--l1d_assoc=2 --l1i_assoc=2
--disk-image=/gem5/system/alpha/m5_system_2.0b3/disks/linux-parsec-2-1-m5.img


Thanks a lot...

Faisal

On Sat, May 6, 2017 at 4:11 AM, Krishna, Tushar 
wrote:

> 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 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 --cpu-type=timing
> --script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby
> --mesh-rows=2 --network=simple --topology=Mesh_XY --caches --l2cache
> --l2_size=512kB --num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB
> --l1d_assoc=2 --l1i_assoc=2
>
> panic: Invalid transition
>
> system.ruby.dma_cntrl0 time: 4722258003 addr: 523845696 event:
> WriteRequest state: BUSY_WR
>
>  @ tick 2361129001500
>
> [doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]
>
> Memory Usage: 1015648 KBytes
>
>
> Thanks a lot.
>
>
> F. A. Faisal
>
>
> On Sat, May 6, 2017 at 2:32 AM, Krishna, Tushar 
> wrote:
>
>> 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  wrote:
>>
>> 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 below config-
>>
>> scons FULL_SYSTEM=1 build/ALPHA/gem5.opt RUBY=true
>> PROTOCOL=MOESI_CMP_directory
>>
>>  ./build/ALPHA/gem5.opt configs/example/fs.py --cpu-type=timing
>> --script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby
>> --mesh-rows=2 --network=garnet2.0 --topology=Mesh_XY --caches --l2cache
>> --l2_size=512kB --num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB
>> --l1d_assoc=2 --l1i_assoc=2
>>
>> It showed me the below error-
>> --
>>
>> panic: Invalid transition
>>
>> system.ruby.dma_cntrl0 time: 4816339893 addr: 525287488 event:
>> WriteRequest state: BUSY_WR
>>
>>  @ tick 2408169946500
>>
>> [doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line
>> 135]
>>
>> Memory Usage: 996944 KBytes
>>
>> Program aborted at tick 2408169946500
>>
>> --- BEGIN LIBC BACKTRACE ---
>>
>> ./build/ALPHA/gem5.opt[0x829015]
>>
>> ./build/ALPHA/gem5.opt[0x839d96]
>>
>> /lib64/libpthread.so.0[0x3685e0f730]
>>
>> /lib64/libc.so.6(gsignal+0x3e)[0x3685a3266e]
>>
>> /lib64/libc.so.6(abort+0x175)[0x3685a33ab5]
>>
>> ./build/ALPHA/gem5.opt[0x6867ac]
>>
>> ./build/ALPHA/gem5.opt[0x631c58]
>>
>> ./build/ALPHA/gem5.opt[0x631e83]
>>
>> ./build/ALPHA/gem5.opt[0x634aad]
>>
>> ./build/ALPHA/gem5.opt[0x8321d1]
>>
>> ./build/ALPHA/gem5.opt[0x852538]
>>
>> ./build/ALPHA/gem5.opt[0x852abb]
>>
>> ./build/ALPHA/gem5.opt[0x7d8d2d]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4e26)[0x369ced55b6]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]
>>
>> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x54f2)[0x369ced5c82]
>>
>> 

Re: [gem5-users] FS simulation with Garnet 2.0

[Krishna, Tushar]

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 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 --cpu-type=timing 
--script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby --mesh-rows=2 
--network=simple --topology=Mesh_XY --caches --l2cache --l2_size=512kB 
--num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB --l1d_assoc=2 
--l1i_assoc=2


panic: Invalid transition

system.ruby.dma_cntrl0 time: 4722258003 addr: 523845696 event: WriteRequest 
state: BUSY_WR

 @ tick 2361129001500

[doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]

Memory Usage: 1015648 KBytes


Thanks a lot.


F. A. Faisal


On Sat, May 6, 2017 at 2:32 AM, Krishna, Tushar 
> wrote:
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 
> wrote:

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 below config-


scons FULL_SYSTEM=1 build/ALPHA/gem5.opt RUBY=true PROTOCOL=MOESI_CMP_directory


 ./build/ALPHA/gem5.opt configs/example/fs.py --cpu-type=timing 
--script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby --mesh-rows=2 
--network=garnet2.0 --topology=Mesh_XY --caches --l2cache --l2_size=512kB 
--num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB --l1d_assoc=2 
--l1i_assoc=2

It showed me the below error-
--

panic: Invalid transition

system.ruby.dma_cntrl0 time: 4816339893 addr: 525287488 event: WriteRequest 
state: BUSY_WR

 @ tick 2408169946500

[doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]

Memory Usage: 996944 KBytes

Program aborted at tick 2408169946500

--- BEGIN LIBC BACKTRACE ---

./build/ALPHA/gem5.opt[0x829015]

./build/ALPHA/gem5.opt[0x839d96]

/lib64/libpthread.so.0[0x3685e0f730]

/lib64/libc.so.6(gsignal+0x3e)[0x3685a3266e]

/lib64/libc.so.6(abort+0x175)[0x3685a33ab5]

./build/ALPHA/gem5.opt[0x6867ac]

./build/ALPHA/gem5.opt[0x631c58]

./build/ALPHA/gem5.opt[0x631e83]

./build/ALPHA/gem5.opt[0x634aad]

./build/ALPHA/gem5.opt[0x8321d1]

./build/ALPHA/gem5.opt[0x852538]

./build/ALPHA/gem5.opt[0x852abb]

./build/ALPHA/gem5.opt[0x7d8d2d]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4e26)[0x369ced55b6]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x54f2)[0x369ced5c82]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]

/usr/lib64/libpython2.6.so.1.0[0x369cef1b9c]

/usr/lib64/libpython2.6.so.1.0(PyRun_StringFlags+0x7a)[0x369cef1daa]

./build/ALPHA/gem5.opt[0x83967f]

./build/ALPHA/gem5.opt[0x415453]

/lib64/libc.so.6(__libc_start_main+0xfd)[0x3685a1f56d]

./build/ALPHA/gem5.opt[0x43b1b1]

--- END LIBC BACKTRACE ---

Aborted (core dumped)



Best regards,

F. A. Faisal


On Fri, May 5, 2017 at 11:22 PM, Krishna, Tushar 
> wrote:
Hi Faisal,
You can still add --topology with the fs.py file.
You need to also add --ruby to run ruby.

For running garnet, you can add a --network=garnet2.0
(Look at options in the garnet2.0 page on the wiki).

Cheers,
Tushar

On May 3, 2017, at 10:50 AM, F. A. Faisal 
> wrote:

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 

Re: [gem5-users] FS simulation with Garnet 2.0

[F. A. Faisal]

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 --cpu-type=timing
--script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby
--mesh-rows=2 --network=simple --topology=Mesh_XY --caches --l2cache
--l2_size=512kB --num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB
--l1d_assoc=2 --l1i_assoc=2

panic: Invalid transition

system.ruby.dma_cntrl0 time: 4722258003 addr: 523845696 event: WriteRequest
state: BUSY_WR

 @ tick 2361129001500

[doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]

Memory Usage: 1015648 KBytes


Thanks a lot.


F. A. Faisal


On Sat, May 6, 2017 at 2:32 AM, Krishna, Tushar 
wrote:

> 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  wrote:
>
> 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 below config-
>
> scons FULL_SYSTEM=1 build/ALPHA/gem5.opt RUBY=true
> PROTOCOL=MOESI_CMP_directory
>
>  ./build/ALPHA/gem5.opt configs/example/fs.py --cpu-type=timing
> --script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby
> --mesh-rows=2 --network=garnet2.0 --topology=Mesh_XY --caches --l2cache
> --l2_size=512kB --num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB
> --l1d_assoc=2 --l1i_assoc=2
>
> It showed me the below error-
> --
>
> panic: Invalid transition
>
> system.ruby.dma_cntrl0 time: 4816339893 addr: 525287488 event:
> WriteRequest state: BUSY_WR
>
>  @ tick 2408169946500
>
> [doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]
>
> Memory Usage: 996944 KBytes
>
> Program aborted at tick 2408169946500
>
> --- BEGIN LIBC BACKTRACE ---
>
> ./build/ALPHA/gem5.opt[0x829015]
>
> ./build/ALPHA/gem5.opt[0x839d96]
>
> /lib64/libpthread.so.0[0x3685e0f730]
>
> /lib64/libc.so.6(gsignal+0x3e)[0x3685a3266e]
>
> /lib64/libc.so.6(abort+0x175)[0x3685a33ab5]
>
> ./build/ALPHA/gem5.opt[0x6867ac]
>
> ./build/ALPHA/gem5.opt[0x631c58]
>
> ./build/ALPHA/gem5.opt[0x631e83]
>
> ./build/ALPHA/gem5.opt[0x634aad]
>
> ./build/ALPHA/gem5.opt[0x8321d1]
>
> ./build/ALPHA/gem5.opt[0x852538]
>
> ./build/ALPHA/gem5.opt[0x852abb]
>
> ./build/ALPHA/gem5.opt[0x7d8d2d]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4e26)[0x369ced55b6]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x54f2)[0x369ced5c82]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]
>
> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]
>
> /usr/lib64/libpython2.6.so.1.0[0x369cef1b9c]
>
> /usr/lib64/libpython2.6.so.1.0(PyRun_StringFlags+0x7a)[0x369cef1daa]
>
> ./build/ALPHA/gem5.opt[0x83967f]
>
> ./build/ALPHA/gem5.opt[0x415453]
>
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x3685a1f56d]
>
> ./build/ALPHA/gem5.opt[0x43b1b1]
>
> --- END LIBC BACKTRACE ---
>
> Aborted (core dumped)
> 
>
> Best regards,
>
> F. A. Faisal
>
>
> On Fri, May 5, 2017 at 11:22 PM, Krishna, Tushar 
> wrote:
>
>> Hi Faisal,
>> You can still add --topology with the fs.py file.
>> You need to also add --ruby to run ruby.
>>
>> For running garnet, you can add a --network=garnet2.0
>> (Look at options in the garnet2.0 page on the wiki).
>>
>> Cheers,
>> Tushar
>>
>> On May 3, 2017, at 10:50 AM, F. A. Faisal  wrote:
>>
>> 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-
>> topology, garnet. Hence, can any one please let me 

Re: [gem5-users] FS simulation with Garnet 2.0

[Krishna, Tushar]

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 
> wrote:

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 below config-


scons FULL_SYSTEM=1 build/ALPHA/gem5.opt RUBY=true PROTOCOL=MOESI_CMP_directory


 ./build/ALPHA/gem5.opt configs/example/fs.py --cpu-type=timing 
--script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby --mesh-rows=2 
--network=garnet2.0 --topology=Mesh_XY --caches --l2cache --l2_size=512kB 
--num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB --l1d_assoc=2 
--l1i_assoc=2

It showed me the below error-
--

panic: Invalid transition

system.ruby.dma_cntrl0 time: 4816339893 addr: 525287488 event: WriteRequest 
state: BUSY_WR

 @ tick 2408169946500

[doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]

Memory Usage: 996944 KBytes

Program aborted at tick 2408169946500

--- BEGIN LIBC BACKTRACE ---

./build/ALPHA/gem5.opt[0x829015]

./build/ALPHA/gem5.opt[0x839d96]

/lib64/libpthread.so.0[0x3685e0f730]

/lib64/libc.so.6(gsignal+0x3e)[0x3685a3266e]

/lib64/libc.so.6(abort+0x175)[0x3685a33ab5]

./build/ALPHA/gem5.opt[0x6867ac]

./build/ALPHA/gem5.opt[0x631c58]

./build/ALPHA/gem5.opt[0x631e83]

./build/ALPHA/gem5.opt[0x634aad]

./build/ALPHA/gem5.opt[0x8321d1]

./build/ALPHA/gem5.opt[0x852538]

./build/ALPHA/gem5.opt[0x852abb]

./build/ALPHA/gem5.opt[0x7d8d2d]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4e26)[0x369ced55b6]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x54f2)[0x369ced5c82]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]

/usr/lib64/libpython2.6.so.1.0[0x369cef1b9c]

/usr/lib64/libpython2.6.so.1.0(PyRun_StringFlags+0x7a)[0x369cef1daa]

./build/ALPHA/gem5.opt[0x83967f]

./build/ALPHA/gem5.opt[0x415453]

/lib64/libc.so.6(__libc_start_main+0xfd)[0x3685a1f56d]

./build/ALPHA/gem5.opt[0x43b1b1]

--- END LIBC BACKTRACE ---

Aborted (core dumped)



Best regards,

F. A. Faisal


On Fri, May 5, 2017 at 11:22 PM, Krishna, Tushar 
> wrote:
Hi Faisal,
You can still add --topology with the fs.py file.
You need to also add --ruby to run ruby.

For running garnet, you can add a --network=garnet2.0
(Look at options in the garnet2.0 page on the wiki).

Cheers,
Tushar

On May 3, 2017, at 10:50 AM, F. A. Faisal 
> wrote:

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- topology, garnet. Hence, 
can any one please let me know how to invoke the garnet 2.0 for full system 
simulation.

Command for previous gem5 with garnet 1.0-

scons build/ALPHA_FS/gem5.opt RUBY=true PROTOCOL=MOESI_CMP_directory


build/ALPHA_FS/gem5.opt configs/example/ruby_fs.py --num-cpus=4 --num-dirs=4 
--num-l2caches=4 --topology=Mesh --mesh-rows=2 --garnet=fixed 
--kernel=vmlinux_2.6.27-gcc_4.3.4 --script=scripts/runparsec1.rcS


Thanks in advance.


F. A. Faisal

___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org

Re: [gem5-users] FS simulation with Garnet 2.0

[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 below config-

scons FULL_SYSTEM=1 build/ALPHA/gem5.opt RUBY=true
PROTOCOL=MOESI_CMP_directory

 ./build/ALPHA/gem5.opt configs/example/fs.py --cpu-type=timing
--script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby
--mesh-rows=2 --network=garnet2.0 --topology=Mesh_XY --caches --l2cache
--l2_size=512kB --num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB
--l1d_assoc=2 --l1i_assoc=2

It showed me the below error-
--

panic: Invalid transition

system.ruby.dma_cntrl0 time: 4816339893 addr: 525287488 event: WriteRequest
state: BUSY_WR

 @ tick 2408169946500

[doTransitionWorker:build/ALPHA/mem/protocol/DMA_Transitions.cc, line 135]

Memory Usage: 996944 KBytes

Program aborted at tick 2408169946500

--- BEGIN LIBC BACKTRACE ---

./build/ALPHA/gem5.opt[0x829015]

./build/ALPHA/gem5.opt[0x839d96]

/lib64/libpthread.so.0[0x3685e0f730]

/lib64/libc.so.6(gsignal+0x3e)[0x3685a3266e]

/lib64/libc.so.6(abort+0x175)[0x3685a33ab5]

./build/ALPHA/gem5.opt[0x6867ac]

./build/ALPHA/gem5.opt[0x631c58]

./build/ALPHA/gem5.opt[0x631e83]

./build/ALPHA/gem5.opt[0x634aad]

./build/ALPHA/gem5.opt[0x8321d1]

./build/ALPHA/gem5.opt[0x852538]

./build/ALPHA/gem5.opt[0x852abb]

./build/ALPHA/gem5.opt[0x7d8d2d]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4e26)[0x369ced55b6]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef)[0x369ced6b7f]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x54f2)[0x369ced5c82]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304)[0x369ced5a94]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927)[0x369ced7647]

/usr/lib64/libpython2.6.so.1.0(PyEval_EvalCode+0x32)[0x369ced7722]

/usr/lib64/libpython2.6.so.1.0[0x369cef1b9c]

/usr/lib64/libpython2.6.so.1.0(PyRun_StringFlags+0x7a)[0x369cef1daa]

./build/ALPHA/gem5.opt[0x83967f]

./build/ALPHA/gem5.opt[0x415453]

/lib64/libc.so.6(__libc_start_main+0xfd)[0x3685a1f56d]

./build/ALPHA/gem5.opt[0x43b1b1]

--- END LIBC BACKTRACE ---

Aborted (core dumped)


Best regards,

F. A. Faisal


On Fri, May 5, 2017 at 11:22 PM, Krishna, Tushar 
wrote:

> Hi Faisal,
> You can still add --topology with the fs.py file.
> You need to also add --ruby to run ruby.
>
> For running garnet, you can add a --network=garnet2.0
> (Look at options in the garnet2.0 page on the wiki).
>
> Cheers,
> Tushar
>
> On May 3, 2017, at 10:50 AM, F. A. Faisal  wrote:
>
> 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-
> topology, garnet. Hence, can any one please let me know how to invoke the
> garnet 2.0 for full system simulation.
>
> Command for previous gem5 with garnet 1.0-
>
> scons build/ALPHA_FS/gem5.opt RUBY=true PROTOCOL=MOESI_CMP_directory
>
> build/ALPHA_FS/gem5.opt configs/example/ruby_fs.py --num-cpus=4 --num-dirs=4 
> --num-l2caches=4 --topology=Mesh --mesh-rows=2 --garnet=fixed 
> --kernel=vmlinux_2.6.27-gcc_4.3.4 --script=scripts/runparsec1.rcS
>
>
> Thanks in advance.
>
>
> F. A. Faisal
>
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
>
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users