Hi All, I have following confusions in the understanding of the checkpointing feature. I am stuck here for quite a while. 1) The page *http://www.m5sim.org/Checkpoints <http://www.m5sim.org/Checkpoints> *says that during restore, gem5 assumes that the checkpoint is taken using atomicSimpleCPU, so we have to mention the cpu-type using --restore-with-cpu. This means that while taking checkpoint also, I should mention the cpu-type. Is my statement correct? 2) Some of the mail chains says that we can take the checkpoint using AtomicSimpleCPU and then upon restore, we can mention the cpu-type along with the cache-configuration.
The above two statements seems contradictory. I tried both, but none of the above two seems to work for me. Both the techniques gives segfault. Can you please help me here? Regards Rahul On Tue, Nov 10, 2015 at 2:12 AM, rahul shrivastava <rshrivasta...@gmail.com> wrote: > Hi All, > > Some of the links suggested that checkpoint should be created using the > default CPU and without any cache configuration as input. I made the > suggested changes in the command, but it still, on restoring, I am getting > the same error. Following is the command that I am executing to take > checkpoint > > ./build/ARM/gem5.fast configs/example/fs.py > --script=./configs/boot/hack_back_ckpt.rcS -n 4 --machine-type=VExpress_EMM > --kernel=../linux-linaro-tracking-gem5/vmlinux > --dtb-filename=../linux-linaro-tracking-gem5/arch/arm/boot/dts/vexpress-v2p-ca15-tc1-gem5_dvfs_per_core_4cpus.dtb > --disk-image=../disks/arm-ubuntu-natty-headless.img --cpu-clock=[1 GHz,750 > MHz,500 MHz] > > > Could you please shed some light? > > > Regards > Rahul > > > > > On Mon, Nov 9, 2015 at 6:51 PM, rahul shrivastava <rshrivasta...@gmail.com > > wrote: > >> Hi All, >> >> I am checkpointing the startup for arm_detailed full system simulation >> using hack_back_ckpt.rcS script. I can see that the checkpoint is created >> successfully, but the restore fails with a seg fault. >> >> : system.remote_gdb.listener: listening for remote gdb on port 7006 >> 0: system.remote_gdb.listener: listening for remote gdb on port 7007 >> Switch at curTick count:10000 >> info: Entering event queue @ 3748342464000. Starting simulation... >> Switched CPUS @ tick 3748342474000 >> switching cpus >> info: Entering event queue @ 3748342474000. Starting simulation... >> Segmentation fault (core dumped) >> >> >> The command to take checkpoint is >> *M5_PATH=$(pwd)/.. ./build/ARM/gem5.fast configs/example/fs.py >> --script=./configs/boot/hack_back_ckpt.rcS --cpu-type=arm_detailed --caches >> -n 4 --l1d_size=32kB --l1i_size=32kB --machine-type=VExpress_EMM >> --kernel=../linux-linaro-tracking-gem5/vmlinux >> --dtb-filename=../linux-linaro-tracking-gem5/arch/arm/boot/dts/vexpress-v2p-ca15-tc1-gem5_dvfs_per_core_4cpus.dtb >> --disk-image=../disks/arm-ubuntu-natty-headless.img --cpu-clock=\['1 >> GHz','750 MHz','500 MHz'\]* >> >> The command to restore is >> *M5_PATH=$(pwd)/.. ./build/ARM/gem5.fast configs/example/fs.py >> --checkpoint-restore=1 --restore-with-cpu arm_detailed --caches -n 4 >> --l1d_size=32kB --l1i_size=32kB --machine-type=VExpress_EMM >> --kernel=../linux-linaro-tracking-gem5/vmlinux >> --dtb-filename=../linux-linaro-tracking-gem5/arch/arm/boot/dts/vexpress-v2p-ca15-tc1-gem5_dvfs_per_core_4cpus.dtb >> --disk-image=../disks/arm-ubuntu-natty-headless.img --cpu-clock=\['1 >> GHz','750 MHz','500 MHz'\]* >> >> >> >> Am I giving some wrong option either while checkpointing or restoring? >> Can you please help me here? >> >> >> Regards >> Rahul >> > >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
