Re: [Gems-users] Initial checkpoints creation problem

["Abdullah Kayi" <apokayi@xxxxxxxxx>]

On Wed, Feb 20, 2008 at 8:59 AM, Dan Gibson <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> 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> wrote:
    

The scripts in their current form only support Simics 2.x

-Derek




On Feb 19, 2008 9:10 PM, Abdullah Kayi <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
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.
    

--
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!

_______________________________________________
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.

-- 
Regards,

Abdullah