[gem5-users] Re: AMD GCN3 - Virtual network type correctness in MOESI_AMD_Base-dir.sm

Hi Sampad, If possible, can you please submit a patch for this? That way Srikant and the others who are experts with Garnet can review and validate. Thanks, Matt On Sun, Aug 30, 2020 at 10:37 PM Sampad Mohapatra via gem5-users < gem5-users@gem5.org> wrote: > Hi Srikant, > > It is used to send

[gem5-users] Re: AMD GCN3 - Virtual network type correctness in MOESI_AMD_Base-dir.sm

Hi Srikant, It is used to send both data and acks. For now I am changing it to response type till a counter argument is presented. Thanks, Sampad Virus-free. www.avast.com

[gem5-users] Re: AMD GCN3 - Virtual network type correctness in MOESI_AMD_Base-dir.sm

Hi Sampad, The vnet_type 'request' and 'response' in vnet is consumed by Garnet for setting the message size. In general, if a message has data that will be transmitted it should be marked as a 'response' type. I am not sure about the GPU_VIPER protocol, but if both the message buffers in question

[gem5-users] AMD GCN3 - Virtual network type correctness in MOESI_AMD_Base-dir.sm

Hi All, The *vnet_type* of the MessageBuffer *responseToDMA* is set as *request* and the virtual network number is set as 3. MessageBuffer * responseToDMA, network="To", virtual_network="3", vnet_type="request"; But in other slicc files such as *GPU_VIPER_TCC.sm* the vnet_type of vn number 3 is

[gem5-users] AMD GCN3 - More virtual networks initialized than required

Hi All, I am using the staging branch. The Viper protocol sets the number of VN to be 11. In GPU_VIPER.py: ruby_system.network.number_of_virtual_networks = 11 But the actual number of VN used is 5. SQC, TCC (has an unused VN #5), TCP, Corepair, Dir all use 0,1,2,3 and 4. The generated stats

[gem5-users] Re: GCN3 docker file missing

Samaksh, Yep, thats precisely what I've been doing. Using the docker from the develop branch, and then the simulator is the staging branch. It actually looks like you pointed the simulator onto the square.cpp source file rather than the square.out (or whatever your compiler outputs). Not sure

[gem5-users] Re: GCN3 docker file missing

Dan or Kyle can confirm, but yes I believe that is what others are doing. If you look through the posted text from running square, you have a fatal error because of it being able to access gem5-resources. Kyle, have you seen this before? Matt On Sun, Aug 30, 2020 at 5:43 PM Samaksh Sethi via

[gem5-users] Re: GCN3 docker file missing

Okay, yeah that does make sense to me. So what i understand is, I used the develop branch for the dockerfile and then I run everything as usual from the staging branch Ok, so that works, Thanks a lot!! I was able to get the build command running, Just one last thing, how do I confirm everything

[gem5-users] Re: GCN3 docker file missing

Ok, we can try to make it clear that you should be looking at the develop branch. I thought the docker was pointing to the GCN3 staging branch, despite being on the develop branch, but that error is likely what this pending patch is fixing:

[gem5-users] Re: GCN3 docker file missing

Thanks! That itself was my issue, I didn't understand from the documentation that I had to clone the develop branch, I was just using the master branch! But I'm still getting errors just running build commands directly from the documentation https://youtu.be/HhLiMrjqCvA - This is the guide I'm

[gem5-users] Re: GCN3 docker file missing

Can you please provide us with some additional information about how you are attempting to run it? For example, what branch are you using? Looks like there is an extra 'o' in that link, thanks -- Kyle can you please fix this? To the best of our knowledge, the Docker is working, so I suspect

[gem5-users] GCN3 docker file missing

I've been trying to run GCN3 for the past few days, but there's some errors rising up. I've tried multiple methods 1. Docker Method http://www.gem5.org/documentation/general_docs/gpu_models/GCN3 Here, the repository link is broken, but if I use the working link