[gem5-users] CXL (Compute Express Link) in gem5?

I'm wondering what work has been done to model CXL in gem5. Is it something that can be modeled with existing gem5 components by adjusting their timing and other parameters, or would modeling it well require new components? From a quick high-level review of what CXL is (Wikipedia), I *think*

[gem5-users] Re: Strange Behavior of checkpoint in multicore

Hi Abdlerhman, One possible explanation is as follows: You are running the same program on all cores with the m5 checkpoint call and then you take at maximum one checkpoint, which will be taken by whichever core hits the checkpoint call first. In the first two cases you mentioned (Atomic vs. O3

[gem5-users] No SE workload is compatible with %s

Hello, I’m trying to run cross compiled for Arm SPECCPU 2017 benchmarks on gem5. I was able to run perlbench, but I tried a few other benchmarks (bwaves, nab, cactuBSSN) and they all gave me this error: ValueError: ('No SE workload is compatible with %s',

[gem5-users] Re: Demo problems

Hi Ayaz - So I’m using the config file in the learning gem5 two level.py. Issues i am getting when i run it:from common import — i get no module named common. I even specify the file path to the common directory to load the cache and still get the same error. I also encounter issues importing

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

Change the virtual network for request, forward, and response to a single vnet (0) in the following files and then set the src/mem/ruby/protocol/Garnet_standalone-cache.sm src/mem/ruby/protocol/Garnet_standalone-dir.sm Then restrict the number of vnets to 1 in configs/ruby/Garnet_standalone.py

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

Yes, please can you help me to modify the files into src/mem/ruby/ as I understand till now, inside garnet 3.0 we have 3 types of messages/classes - requests - forward - response. Each one of these classes has its own virtual network separated from the other classes. - requests, and

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

Hi Karim, The virtual network is the protocol level sub network. The virtual channels indicate the number of parallel buffer streams in each virtual network. To achieve a protocol deadlock you will have to set a single virtual network and then force the different types of messages (request,

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

hi, The virtual networks are mainly used for avoiding protocol deadlocks, i.e., one message type per vnet. the output 5 virtual channels is because you set vcs-per-vnet=1(i.e., one virtual channel per vnet) and the garnet model has 5 virtual networks (I think so) As for the last problem, it's

[gem5-users] Gem5 - garnet 3.0 - Mesh_XY - Deadlock

Hey everyone, For learning purposes, I'm trying to understand the deadlock and virtual channels, so in gem5/garnet 3.0 in file mem/ruby/network/garnet/InputUnit.cc I have tried to output the following: std::cout << " - VCs " << m_router->get_num_vcs() << " Vnetworks: " << m_router->get_num_vnets()