gem5-resources
gem5-resources copied to clipboard
gem5
resources: SPEC 2017 benchmark suite on ARM64 Ubuntu 22.04 Disk Image
This pull request adds the files and instructions needed to make a ARM64 Ubuntu 22.04 disk image, and to install the SPEC 2017 benchmark suite on the disk image. The qemu-files directory contains the files for getting the disk image and launching it as a QEMU instance. The packer-files directory contains the files that Packer needs to build the disk image, as well as a script for obtaining Packer. README.md contains detailed instructions on how to build the disk image and install SPEC 2017 using the scripts and files provided.
I tested this by running a few gem5 simulations with the disk image that I made to figure out the process of building the disk image. Next, I launched the disk image as a QEMU instance and checked if the benchmarks that had built successfully would run. Finally, I built another disk image as part of writing the documentation, and used it as a resource to run another gem5 simulation.
Hi @erin-le , The documentation you provided is not elaborate on adding the gem5-resource file. Do you have the launch script that you use to launch the disk with gem5 as a resource ?
configs/example/gem5_library/x86-spec-cpu2017-benchmarks.py should work. There's also a 2006 version as well.
@powerjg But that uses x86 boards and other configs that are used for x86. How is that going to work with ARM+KVM gem5 with SPEC2017 ?
Oh, sorry. I didn't look closely enough. We don't have any scripts out of the box for Arm+SPEC. However, you should be able to use the x86 one as a good example.
Hi Jason @powerjg , Thanks for the reply. However, I have tried multiple iterations of trying to generate an ARM version but it fails. Specifically, because I am trying to boot into a KVM version, and I am trying to follow arm-ubuntu-run-with-kvm.py, but it fails to boot. There are panic errors, segmentation faults. I am trying to start without a kvm, even that fails to boot. Are there any starting scripts or any efforts you know of to follow this for SPEC2017 (similar to x86-SPEC2017) @BobbyRBruce ?