Re: [Gems-users] Old question is repeated: Initial checkpoints creation problem


Date: Tue, 6 Jan 2009 09:38:27 -0600
From: "Dan Gibson" <degibson@xxxxxxxx>
Subject: Re: [Gems-users] Old question is repeated: Initial checkpoints creation problem
When last I checked, which was quite some time ago, Simics 2.2.19 was still available from Virtutech's website (www.simics.net), though it required some website spelunking. If that is not the case now, it would be good to know for sure.

Regards,
Dan

On Tue, Jan 6, 2009 at 9:24 AM, Xiongfei Liao <xiongfei.liao@xxxxxxxxx> wrote:
Hi,

I met the same problem when I tried to generate "naked checkpoints" using the shell script in GEMS release.

Dan provided a quick solution. But I have a question: where and how can I get the version 2.2.19 of Simics?

Thanks.

Xiongfei



Re: [Gems-users] Initial checkpoints creation problem


Date: Wed, 20 Feb 2008 13:54:14 -0600
From: Dan Gibson <degibson@xxxxxxxx>
Subject: Re: [Gems-users] Initial checkpoints creation problem
In general, you should always use the most recent version if you can. We use 2.2.19 internally, so the most recent version of GEMS is fully compatible with Simics 2.2.19. But, you needn't bother interface GEMS to Simics 2.2.19 if you're only using Simics 2.2.19 to make checkpoints -- you can do your timing simulation under Simics 3.0.x.
Regards,
Dan

Abdullah Kayi wrote:
Which version of GEMS would be better with simics 2.2.19? The setup for 2.2.X in the wiki points to a really old version (1.0).
Thanks,

Abdullah

On Wed, Feb 20, 2008 at 8:59 AM, Dan Gibson <degibson@xxxxxxxx <mailto:degibson@xxxxxxxx>> wrote:
    As I recall there is a huge difference in the machine
specification between Simics 2.x and Simics 3.x. I suggest you
make the checkpoints with 2.2.19, and then simulate using 3.0.30.
Checkpoints are forward-compatible.

Regards,
Dan


Derek Hower wrote:
    I would recommend using 2.2.19, as that is the version the scripts
were created on. There is no patch for 3.x to my knowledge, though if
you are feeling ambitious there are some comments in the current
scripts indicating what needs to be done:)

-Derek

On Feb 19, 2008 9:36 PM, Abdullah Kayi <apokayi@xxxxxxxxx> <mailto:apokayi@xxxxxxxxx> wrote:
    Thanks for the reply. Does anybody have patches for Simics3.0.x? Or would it
be better to try simics 2.2.19 available on simics web-site for other
compatibility issues?

Regards,

Abdullah



On Feb 20, 2008 12:22 AM, Derek Hower <drh5@xxxxxxxxxxx> <mailto:drh5@xxxxxxxxxxx> wrote:
    The scripts in their current form only support Simics 2.x

-Derek




On Feb 19, 2008 9:10 PM, Abdullah Kayi <apokayi@xxxxxxx> <mailto:apokayi@xxxxxxx> wrote:
    Hi all,

Sorry to bother for a potentially simple question. I tried to create
checkpoints using the script provided in $GEMS/checkpoints
(naked-check-create.sh) as explained in the README file of corresponding
directory. In order to do that, I downloaded and tried both Solaris10
(sol-10-u4-ga-sparc-v[1,2]-iso.zip) and Solaris Express
(sol-nv-b79b-sparc-v[1,2]-iso.zip) cd images. I am getting the following
warning and error after that.

Machines based on serengeti_conf.py are only provided for backward
compatibility. The new component based machines in simics/targets/
are recommended instead.

Serengeti configuration error:
Unsupported cpu type: ultrasparc-iii+

System info: gems2.0, simics3.0.30, x86_linux

Should I try to get some earlier versions of Solaris? Or should I
    enforce
    cpu_class to be something like ultrasparc-iii? Basically, I only
    modified
    system.conf with necessary modifications but nothing else as mentioned
    in the
    README file.

Regards,

Abdullah
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding
    "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
    _______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding
    "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
    --
Regards,

Abdullah
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding
"site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.



    _______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.


-- http://www.cs.wisc.edu/~gibson <http://www.cs.wisc.edu/%7Egibson> [esc]:wq!
    _______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx <mailto:Gems-users@xxxxxxxxxxx>
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding
"site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.





--
Regards,

Abdullah
------------------------------------------------------------------------

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.



_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.





--
http://www.cs.wisc.edu/~gibson [esc]:wq!
[← Prev in Thread] Current Thread [Next in Thread→]