[gem5-users] Re: [EXT] Re: Success with GPU

2025-03-02 Thread Beser, Nicholas D. via gem5-users
Thank you, I will take a look at these. Nick From: Matt Sinclair Sent: Sunday, March 2, 2025 5:31 PM To: Beser, Nicholas D. Cc: The gem5 Users mailing list ; Jason Lowe-Power Subject: Re: [EXT] Re: [gem5-users] Success with GPU APL external email warning: Verify sender mattdsinclair.w...@gm

[gem5-users] Re: [EXT] Re: Success with GPU

2025-03-02 Thread Matt Sinclair via gem5-users
Whoops, thanks. I meant this one: https://github.com/gem5bootcamp/2024/tree/main/materials/04-GPU-model. Note in these commands we actually specified the full path to gem5-vega in them (we also didn't need the docker in this case because of how Jason set things up). I do not know though if that s

[gem5-users] Re: [EXT] Re: Success with GPU

2025-03-02 Thread Beser, Nicholas D. via gem5-users
Matt, No I did not run those commands. I had not seen them before. They are not setup for the repository I am working from (they look like they are setup for bootcamp 2022). Nick From: Matt Sinclair Sent: Sunday, March 2, 2025 4:49 PM To: Beser, Nicholas D. Cc: The gem5 Users mailing list ;

[gem5-users] Re: [EXT] Re: Success with GPU

2025-03-02 Thread Matt Sinclair via gem5-users
Hi Nick, In regards to gem5-vega-se, the ls you sent before shows it does not exist in /usr/local/bin, so it's not surprising that didn't work. In regards to docker more broadly though, setting up volumes is tricky. The mental model I always have is: with this volume I specify, is everything I ne

[gem5-users] Re: [EXT] Re: Success with GPU

2025-03-02 Thread Matt Sinclair via gem5-users
Hi Nick, Did you try setting up the docker volume to explicitly include /usr/local/bin then? The reason (likely) why it worked after you compiled gem5.opt explicitly is that the folder you built it in was explicitly included in the docker volume. Unless you are saying you built gem5.opt for VEGA

[gem5-users] Re: Success with GPU

2025-03-02 Thread Matt Sinclair via gem5-users
Hi Nick, I'm not sure why you believe gem5-vega should be in /usr/local/bin? It's been a few months since I last looked at this codespace, but looking at the instructions here: https://github.com/gem5bootcamp/gem5-bootcamp-env/blob/51590ae00b0e451c9b6a8854addbb94128ab4cac/materials/developing-gem5

[gem5-users] Re: [EXT] Re: Success with GPU

2025-03-02 Thread Beser, Nicholas D. via gem5-users
Matt, Here is codespace with ls -l /usr/local/bin root@codespaces-e992b2:/workspaces/en525-712-81-sp25-amd-gpu-using-gem5-gem5bootcamp2024# ls -l /usr/local/bin total 3274048 lrwxrwxrwx 1 root root 36 Feb 26 00:48 actionlint -> /usr/local/lib/actionlint/actionlint -rwxrwxr-x 1 ubunt

[gem5-users] Success with GPU

2025-03-02 Thread Beser, Nicholas D. via gem5-users
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 $(pw