Even running bzip2 without checkpoints, the simulation seems to freeze:

$ ./start_sim ; <bzip2 with params> ; ./stop_sim ;

The freeze occurs at:

Completed       2726000 cycles,       1960176 commits:    482598 Hz,
 355575 insns/sec: rip ffffffff812a1825spec_init
  Completed      67921000 cycles,      83616859 commits:    284637 Hz,
 359909 insns/sec: rip ffffffff8114e969

The stats do not seem to increase after this. Please do let me know if I am
missing something.

I am currently evaluating marss86 to see if I can use it for my research.
So I am just playing around with the different features.

Thanks for your help!

Regards,
Ankita

On Fri, Sep 7, 2012 at 11:20 AM, Ankita (Garg) Goel <[email protected]>wrote:

> Hi,
>
> I am new to marss86. I am trying to create checkpoints for the bzip2
> benchmark. The details of what I have done so far is:
>
> # qemu/qemu-system-x86_64 -m 2048M -hda images/ubuntu.img -simconfig
> spec.cfg
>
> where, spec.cfg just contains "-machine single_core -stats stats.txt".
>
> Inside the guest, I do the following to create the checkpoint:
>
> $ create_checkpoints bzip ; <bzip2_command> <params>; sudo ../stop_sim;
>
> It seems to create the checkpoint and marss exits. Now, I do the following
> as directed:
>
> $ qemu/qemu-system-x86_64 -m 2048M -hda ~/images/ubuntu.img -simconfig
> bzip.cfg
>
> where, bzip.cfg is:
>
> -machine single_core
> -logfile sc.log
> -stats stats.txt
> -simpoint t.simpoints
> -simpoint-interval 10000
> -simpoint-chk-name bzip
>
> I get the following:
> Simulator is now waiting for a 'run' command.
> VNC server running on `127.0.0.1:5900'
> MARSSx86::Creating checkpoint bzip_sp_0
> MARSSx86::Checkpoint bzip_sp_0 created
>
> It seems to be stuck at this point for over 3-4 hours. Is that expected ?
> Am I missing some steps ?
>
> Appreciate any help on this.
>
> --
> Regards,
> Ankita
>
>
_______________________________________________
http://www.marss86.org
Marss86-Devel mailing list
[email protected]
https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel

Reply via email to