I teach a advanced computer architecture class for the whiting school of 
engineering at Johns Hopkins University. We use the enterprise github codespace 
to run the bootcamp 2024 as part of the class. I tried to setup the codespace 
for my class this morning and discovered that some of the resources do not seem 
to be accessible. The script On_create.sh is missing :

wget 
https://storage.googleapis.com/dist.gem5.org/dist/v24-0/gpu-fs/kernel/vmlinux-gpu-ml-isca

# Note: this unzips to 55 GB so must in on /tmp.
# See post_start.sh where it is unzipped each time the devcontainer starts
wget 
https://storage.googleapis.com/dist.gem5.org/dist/v24-0/gpu-fs/diskimage/x86-ubuntu-gpu-ml-isca.gz

I use these items to simulate the GPU exercises.

Is there a revised On_create.sh file? Has anyone run into these problems?

Please let me know. It is interfering with setting up the basic codespace.

Thank-you,

Nick Beser
Email: [email protected]<mailto:[email protected]>

The current On_create.sh:


#!/bin/bash

# Update the submodules
git submodule update --init --recursive

# Setups the gem5 source directory
pushd gem5

## We cleanup git's 'blame' feature by ignoring certain commits (typically
## commits that have reformatted files)
git config --global blame.ignoreRevsFile .git-blame-ignore-revs

## `git pull` should rebase by default
git config --global pull.rebase true

./util/pre-commit-install.sh

popd # gem5

# Pre-download the resources we use

gem5 pre-download-resources.py

docker pull ghcr.io/gem5/gcn-gpu:v24-0

wget http://dist.gem5.org/dist/v24-0/test-progs/square/square

wget 
https://storage.googleapis.com/dist.gem5.org/dist/v24-0/gpu-fs/kernel/vmlinux-gpu-ml-isca

# Note: this unzips to 55 GB so must in on /tmp.
# See post_start.sh where it is unzipped each time the devcontainer starts
wget 
https://storage.googleapis.com/dist.gem5.org/dist/v24-0/gpu-fs/diskimage/x86-ubuntu-gpu-ml-isca.gz


_______________________________________________
gem5-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to