Hello all,
I've been trying to use gem5's example configuration in configs/example/arm/starter_fs.py with the HPI model with the following options: --cpu hpi --num-cores 2 --disk-image $M5_PATH/disks/debian_aarch64_base.img --kernel $M5_PATH/binaries/vmlinux-gem5-4.20.0-hopwood --dtb $M5_PATH/binaries/armv8_gem5_v1_2cpu.20170616.dtb It seems to run fine with --num-cores 1 and the single core dtb, but if I try with --num-cores 2 and the dual core dtb, it eventually reports simulate limit reached. It seems like this bug doesn't get triggered when I use ext2 for my partition (using ext4 does trigger it) and disabling the ext2/3 and enabling using ext4 driver for ext2 in the kernel configuration. I have not figured out yet why the ext drivers are triggering the bug. Has anyone else seen "simulate limit reached" for HPI with multicore? Has anybody found the real issue? Any help is appreciated. Thanks, Chris _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
