Update. I was reading a related discussion in the archive (https://www.mail-archive.com/[email protected]/msg19217.htm) where the OP reported they could successfully run kvm up to 8 cores with the configs/example/arm/fs_bigLITTLE.py script. So I tried running gem5 with his parameters and the arm/fs_bigLITTLE.py.
The following boots correctly: ./build/ARM/gem5.opt configs/example/arm/fs_bigLITTLE.py --kernel $M5_PATH/binaries/vmlinux.arm64 --machine-type VExpress_GEM5 --disk /scratch/pedro/ubuntu-18.04-arm64-docker.img --cpu-type kvm --big-cpus 4 But the following do not (boot get stuck right in the beginning): ./build/ARM/gem5.opt configs/example/fs.py --kernel $M5_PATH/binaries/vmlinux.arm64 --machine-type VExpress_GEM5 --disk-image /scratch/pedro/ubuntu-18.04-arm64-docker.img --cpu-type ArmV8KvmCPU --num-cpus 4 So I think there might be something I can adapt from fs_bigLITTLE to run with fs.py. Any hints on this are welcome, but I still need to review the differences, so it might be simple to fix. The main problem I still have is fs_bigLITTLE.py with --big-cpus 8 (I want to have an 8-core setup) causes panic: info: Using bootloader at address 0x10 info: Using kernel entry physical address at 0x80080000 info: Loading DTB file: m5out/system.dtb at address 0x88000000 info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. info: KVM: Coalesced MMIO disabled by config. panic: KVM: Failed to create virtual CPU Memory Usage: 2619720 KBytes Program aborted at tick 0 --- BEGIN LIBC BACKTRACE --- ./build/ARM/gem5.opt(_Z15print_backtracev+0x40)[0x5576c8e090] ./build/ARM/gem5.opt(_Z12abortHandleri+0x5c)[0x55770cbdb4] linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0x7f9b01e6c0] /lib/aarch64-linux-gnu/libc.so.6(raise+0xb0)[0x7f9abe94f8] --- END LIBC BACKTRACE --- Aborted (core dumped) I saw some discussion on gem5 supporting gicv2 but not gicv3, but from what I read even the former should support up to 8 cores. So I'm not sure this is the problem here. Any suggestions? Thanks, Pedro. _______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
