resources: GPUFS: ROCm 7.0 and MI350 support

[abmerop]

Intended to be merged with v25.1 release

[powerjg]

lgtm @Harshil2107 can you generate a new version?

@abmerop Is this intended to replace the current disk image as a new version or to live alongside? If the latter, then we should duplicate the files.

[Harshil2107]

I will upload the new version. I noticed the disk image has the same name as the already existing gpu image. Are the kernel and the disk extracted from this image supposed to replace the already existing disk and kernel or should they be added an new resources?

[abmerop]

I am not aware of any existing resources.

[mattsinc]

Looks good to me too!

[Harshil2107]

I am not aware of any existing resources.

We have the following disk and kernel already upload to resources that were made from the source that was updated in this PR.

• https://gem5dist.blob.core.windows.net/dist/v24-0/gpu-fs/diskimage/x86-ubuntu-gpu-ml.gz
• https://gem5dist.blob.core.windows.net/dist/v24-0/gpu-fs/kernel/vmlinux-gpu-ml.gz

would it be ok to replace these resouces with the updated ones created from this PR? or do we want to create a new copy?

[abmerop]

I am not aware of any existing resources.

We have the following disk and kernel already upload to resources that were made from the source that was updated in this PR.

• https://gem5dist.blob.core.windows.net/dist/v24-0/gpu-fs/diskimage/x86-ubuntu-gpu-ml.gz
• https://gem5dist.blob.core.windows.net/dist/v24-0/gpu-fs/kernel/vmlinux-gpu-ml.gz

would it be ok to replace these resouces with the updated ones created from this PR? or do we want to create a new copy?

Ah ok. I think I see you point then. How about I rename the output that would be created in this PR to include the ROCm version? I am not sure what version is on those disks without downloading it.

[abmerop]

Changed script to name the output files with the major/minor version of ROCm. In this case the disk would be x86-ubuntu-rocm70 and vmlinux-rocm70.

The disk/kernel uploaded is ROCm 6.1. If you wanted to retroactively rename it (maybe via symlink, http/301, etc. to avoid dead links).