You could also enable Minor debug messages with --debug-flags MinorCPU and see if they show, or put a GDB breakpoint / print on the tick function, this way you can't be wrong.
On Thu, Oct 31, 2019 at 9:07 PM Iago . <[email protected]> wrote: > > I have been using gem5 to study a couple control algorithms performances for > a future prototype using an ARM board and so I'm trying to use the HPI cpu > model but had errors occur when I tried to boot it with more then 1 cpu, so > I'm trying to do what I found on the message board of creating a checkpoint > with AtomicSimpleCPU through the following command: > build/ARM/gem5.opt configs/example/fs.py > --disk-image=linaro-minimal-aarch64.img --kernel=vmlinux.vexpress_gem5_v1_64 > --machine-type=VExpress_GEM5_V1 --dtb=armv8_gem5_v1_4cpu.dtb > --cpu-type=AtomicSimpleCPU --num-cpus=4 --mem-type=LPDDR2_S4_1066_1x32 > --mem-size=1GB --caches --l2cache --l2_size=512kB --l1i_size=16kB > --l1d_size=16kB --cpu-clock=1.4GHz --restore-with-cpu=HPI > --script=hackback.rcS > > And restoring the created checkpoint through: > build/ARM/gem5.opt configs/example/fs.py > --disk-image=linaro-minimal-aarch64.img --kernel=vmlinux.vexpress_gem5_v1_64 > --machine-type=VExpress_GEM5_V1 --dtb=armv8_gem5_v1_4cpu.dtb --cpu-type=HPI > --num-cpus=4 --mem-type=LPDDR2_S4_1066_1x32 --mem-size=1GB --caches --l2cache > --l2_size=512kB --l1i_size=16kB --l1d_size=16kB --cpu-clock=1.4GHz > --restore-with-cpu=HPI --script=test.rcS -r 8 > > Is there any way to check for sure if the restored checkpoint is using the > HPI cpu model? > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
