Hi all, This is a very basic and perhaps silly question. I’m trying to take checkpoints in a gem5 program so that I can debug a particular segment of the execution more efficiently, but it seems that the flag seems to pause the execution of the environment and not actually take any checkpoints.
I’m currently working from commit 87c121fd954ea5a6e6b0760d693a2e744c2200de (i.e., v21.1.0.0) And am running the following command line: build/X86/gem5.opt -d $CURR_DIR/debug $CURR_DIR/configs/example/fs.py --caches --l2cache --mem-type DDR3_1600_8x8 --mem-size 2GB --meta-size 512kB --num-cpus 4 --disk-image $DISK_PATH --kernel $KERNEL_PATH --cpu-type $CPU_TYPE --script=$SCRIPT_PATH --l2_size=1MB --take-checkpoints=10000,20000 I assumed that --take-checkpoints was the proper way to do this, but it seems that the execution pauses at this point and no checkpoint files are produced in the out directory. Is there something that I’m doing wrong or a better way to go about doing this? Thanks for your help! Best, Sam _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
