GEM5 aarch64

README.adoc

@@ -1401,6 +1401,13 @@ Internals:
 
 * networking not working
 
+==== GEM5 aarch64
+
+....
+./configure && ./build -a aarch64 -g
+./run -a aarch64 -g
+....
+
 ==== GEM5 x86
 
 TODO didn't get it working yet.

build-gem5

@@ -23,7 +23,7 @@ if [ "$arch" = x86_64 ]; then
   # This file must always be present, despite --kernel overriding that default and selecting the kernel.
   # I'm not even joking. No one has ever built x86 gem5 without the magic dist dir present.
   touch "${binaries_dir}/x86_64-vmlinux-2.6.22.9"
-elif [ "$arch" = arm ]; then
+elif [ "$arch" = arm ] || [ "$arch" = aarch64 ]; then
   # Compilation fails with gcc 7 on that commit.
   # There were some recent portability patches, so it will likely get there soon.
   CC=gcc-6 CXX=g++-6 scons -j"$(nproc)" --ignore-style build/ARM/gem5.opt

buildroot_config_fragment

@@ -9,6 +9,7 @@ BR2_ROOTFS_POST_BUILD_SCRIPT="../rootfs_post_build_script"
 BR2_ROOTFS_POST_IMAGE_SCRIPT="../rootfs_post_image_script"
 BR2_ROOTFS_USERS_TABLES="../user_table"
 BR2_TARGET_ROOTFS_CPIO=y
+BR2_TARGET_ROOTFS_EXT2=y
 
 # Host GDB
 BR2_GDB_VERSION="7.11.1"

run

@@ -65,7 +65,7 @@ M5_PATH='$(pwd)/gem5/gem5-system' \
 --kernel='${outdir}/build/linux-custom/vmlinux' \
 --root-device=/dev/sda \
 "
-  elif [ "$arch" = arm ]; then
+  elif [ "$arch" = arm ] || [ "$arch" = aarch64 ]; then
     cmd="\
 M5_PATH='$(pwd)/gem5/gem5-system' \
 $debug_vm \
@@ -73,7 +73,7 @@ $debug_vm \
 '${gem5_dir}/configs/example/fs.py' \
 --command-line='earlyprintk=pl011,0x1c090000 console=ttyAMA0 lpj=19988480 rw loglevel=8 mem=512MB root=/dev/sda $extra_append' \
 --disk-image='${outdir}/images/rootfs.ext2' \
---dtb-file='${gem5_dir}/system/arm/dt/armv7_gem5_v1_1cpu.dtb' \
+--dtb-file='${gem5_dir}/system/arm/dt/$([ "$arch" = arm ] && echo armv7_gem5_v1_1cpu || echo armv8_gem5_v1_1cpu).dtb' \
 --kernel='${outdir}/build/linux-custom/vmlinux' \
 --machine-type=VExpress_GEM5_V1 \
 "