Can you run it without network=garnet and check?

My guess is that this has nothing to do with the network but instead the fact 
that the arm isa does not work with ruby. Others can probably confirm this.

Cheers,
Tushar

On Apr 11, 2018, 4:00 PM -0400, SHARJEEL KHILJI 
<sharjeelsaeedkhi...@gmail.com>, wrote:
Hello,

SIr, I want to run 16 core ARM big LITTLE NoC Mesh_XY with one ex5_big core and 
15 ex5_small cores. The build statement for the NoC is as follows.

./build/ARM/gem5.fast   configs/example/fs_het.py  --l1d_size=128kB 
--l1i_size=128kB  --num-l2caches 16 --num-bigl2caches 1 --num-littlel2caches 15 
--l2_bigsize 32MB  --l2_littlesize 16MB  --cacheline_size=64 
--machine-type=VExpress_GEM5_V1  --kernel 
/home/khilji/gem5/m5/system/binaries/vmlinux-aarch32 --disk-image 
/home/khilji/gem5/m5/system/disks/arm-ubuntu-natty-headless.img --dtb-filename 
/home/khilji/gem5/m5/system/dtb/armv7_gem5_v1_16cpu.dtb  --num-cpus 16    
--ruby --num-dirs=16 --network=garnet2.0 --topology Mesh_XY  --mesh-rows 4 
--mem-size 1GB

When I run this NoC with 16 cores I get following deadlock in the vc_busy_count.


 panic condition vc_busy_counter[vnet] > m_deadlock_threshold occurred: 
system.ruby.network.netifs00: Possible network deadlock in vnet: 0 at time

Any suggestions Sir?

regards,
Sharjeel
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to