Based on the discussion, It seems that docker can't find the gem5-vega that is
in the /usr/local/bin. I noticed that the instructions also had us building the
VEGA_X86/gem5.opt binary with the following command:
I. docker run --volume $(pwd):$(pwd) -w
$(pwd) ghcr.io/gem5/gcn-gpu:v24-0 scons build/VEGA_X86/gem5.opt -j# (# is the
number of cores on your X86 system)
I build VEGA_X86 in codespace. The following command afterwards was able to run
the GPU square binary:
docker run --volume $(pwd):$(pwd) -w $(pwd) ghcr.io/gem5/gcn-gpu:v24-0
gem5/build/VEGA_X86/gem5.opt gem5/configs/example/apu_se.py -n 3 -c
gem5-resources/src/gpu/square/bin/square
The program exsecuted correctly and create a stats.txt file. I have sent this
instruction to my class so they could proceed with the experiments using the
GPU.
I do have a question about the results in the stats.txt file. We noticed that
the program computed the square operation using the GPU, and then compared the
result using a CPU only code. When one of my students disabled the CPU only
code, he did not see a drop in the cpu instructions that would have
corresponded to that loop. I have them looking at the stats.txt file for
indications about what resources the GPU had used to perform the operation.
Nick
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
