Hi Jason,
Checkpoints are typically made by "booting" a simulated machine. To do
this, have a look at the various machine specification files that come
with Simics (version 2.2.19)... they reside in simics/home/sarek. They
will set up the various parts of the machine: memories, processors,
disks, etc. Some of them reference image files (eg. the contents of the
disks), which you usually make yourself by installing an OS on the
simulated machine. Documentation and scripts for installing an OS is
part of the simics tarball.
It is essential that you use the "sarek" target when using GEMS, which
is a serengeti (Sun/SPARC) machine. Ruby (the memory hierarchy
simulator) expects to interface with the sarek configuration.
If you have any specific GEMS questions, go ahead and post them to the
list (include things like specific error messages, etc.). Please direct
*simics* questions to the simics forums provided by virtutech, found at
www.simics.net.
To address your specific issue, load-module ruby will fail (pre-opal) IF
there is no "phys_mem0" object for ruby to attach to. Most likely, this
is due to a bad checkpoint. Have a look at the Simics Target Guide:
Serengeti (PDF) distributed with Simics 2.2.19.
Good luck!
Regards,
Dan Gibson
jloew@xxxxxxxxxxxxxxxxx wrote:
I was wondering if anyone can help me to figure out how to create a
checkpoint (such that I can complete the tasks listed in the documentation
wiki: http://www.cs.wisc.edu/gems/doc/wiki/moin.cgi/QuickStart).
The information about checkpointing that I got from the Virtutech FAQs let
me to create a configuration that doesn't allow me to use setparam with
ruby (load-module ruby fails unless I use load-module opal first but
either way I can't get it to work - all the installation steps appeared to
work up to the point of loading the checkpoint).
Any help would be appreciated,
--
http://www.cs.wisc.edu/~gibson [esc]:wq!
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}