GCN3 GPU can not work
following the guide by http://www.gem5.org/documentation/general_docs/gpu_models/GCN3, I build the docker of GCN3_X86 gem5, when run the square case, the simulator will report error:
Forcing maxCoalescedReqs to 32 (TLB assoc.)
fatal: system.cpu2.CUs0 does not have any port named gmTokenPort
gem5 version is the latest tag: v18.104.22.168
chen boya indicated this worked for him.
Can we close this now that 21.0 is released?
Yeah, I created a patch to fix the above points in the documentation (https://gem5-review.googlesource.com/c/public/gem5-website/+/43565) as well as to mention that there’s a pre-built docker image.
HIP is currently installed from the pre-built binaries instead of from source (It’s installed on lines 68-69 on the current Dockerfile on develop), as we were able to remove the hacks Matt mentioned. This also fixed a race condition we were encountering.
: thanks for bringing this changes to our attention. , I believe the first two points Mingzhe raised, should just be fixed in the documentation, right?
Regarding the other two questions:
Currently GCN3 support only works for ROCm 1.6, which requires gcc 5.4, which in turn works best in Ubuntu 16. There may be workarounds/hacks to get it working in newer versions of Ubuntu, but there is no ETA for when a newer version of Linux would be supported (since it would require getting a newer version of ROCm working). We are instead (mostly) working on getting FS mode working with ROCm, which elides the need to get every single syscall implemented properly for each version of ROCm.
I’m not sure what “versions to versions” means in your comment. Maybe you mean different commits that updated this file? Either way, we changed how HIP was installed as we found ways to remove some hacks we’d added to get HIP working (e.g., manually removing memory copies). , I believe the current Docker just installs HIP directly from apt-get, right?
: if you can point us to where you thought the instructions said to use the branch you were using, that would be most helpful. I had updated the instructions to hopefully resolve this confusion last week, but it seems not all was resolved.