After spending several hours to guess what was wrong, here are my findings:
It seems that if I set PhysicalMemory as 512MB, checkpointing can work.
However, if I set it as 4096MB (I did this because SPECCPU2006 requires at
least 2GB free memory), checkpoint will not work. The place I changed this
is in common/example/se.py
system = System(cpu = [CPUClass(cpu_id=i) for i in xrange(np)],
physmem = PhysicalMemory(range=AddrRange("4096MB")),
membus = Bus(), mem_mode = test_mem_mode)
Could anyone give some suggestions?
Thanks!
-Sheng
On Wed, Feb 9, 2011 at 12:05 AM, Sheng Li <[email protected]> wrote:
> Hi Guys,
>
> I tried to use checkpoints in M5 but could not have it work. I used
> ALPHA_SE.
>
> The commands I use to create/resume checkpoints are M5 outputs are:
>
> Creating checkpoint:
> ______________________
> [sli2@newcell ~/m5-work-stable]$ ./build/ALPHA_SE/m5.opt
> configs/example/se.py --bench bzip2 --take-checkpoint=2200 --at-instruction
> ...
> command line: ./build/ALPHA_SE/m5.opt configs/example/se.py --bench bzip2
> --take-checkpoint=2200 --at-instruction
> 2200000000
> Global frequency set at 1000000000000 ticks per second
> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
> Creating checkpoint at inst:2200
> info: Entering event queue @ 0. Starting simulation...
> info: Increasing stack size by one page.
> hack: be nice to actually delete the event here
> exit cause = a thread reached the max instruction count
> Writing checkpoint
> Checkpoint written.
> Exiting @ cycle 1111000 because a thread reached the max instruction count
>
> Resume checkpoint:
> _________________________
> command line: ./build/ALPHA_SE/m5.opt configs/example/se.py --bench bzip2
> --checkpoint-restore=2200 --at-instruction
> 2200000000
> Global frequency set at 1000000000000 ticks per second
> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
> warn: optional parameter system.cpu.workload:M5_pid not present
> For more information see: http://www.m5sim.org/warn/aa78cda1
> **** REAL SIMULATION ****
> info: Entering event queue @ 1111000. Starting simulation...
> hack: be nice to actually delete the event here
> Exiting @ cycle 1111500 because halt instruction encountered <--Here is
> the problem.
>
> Any help would be highly appreciated!
>
> Thanks
> -Sheng
>
>
>
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
