interface.C compiles under 3.0.x. I have not personally tested this
functionality under Simics 3.0.x, nor am I aware of anyone else having
tested. There might be differences in which accesses are observed or not
between Simics 2.2.X and 3.0.x.
After the GEMS 1.3.1 patch, the variable names should be correct, but
that doesn't guarantee that it will work.
As far as save-caches, it will be tags only (as ruby does not support
data at the moment anyway).
Regards,
Dan
Thomas Yeh wrote:
On Tue, 24 Oct 2006, Dan Gibson wrote:
Have a look at SIMICS_remove_timing_model in interface.C. Be aware it
might be a slightly deprecated, but it does the trick for Simics 2.2.x.
I am running simics 3.0.19. Would this still work?
Is save-caches and load-caches the way to save and warmup cache state?
instead of dump-data?
What exactly is saved with save-caches? just the tags? or both tag and
data?
thx,
Regards,
Dan
Thomas Yeh wrote:
I have another related question:
Is there a way to switch the sending of memory accesses to ruby on and
off?
On Tue, 24 Oct 2006, Thomas Yeh wrote:
thx for the info. I just looked in the code and saw that there is no code
inside printdata().
If I just want to save the cache state for warmup purpose on future runs,
should I just use ruby0.save-caches? and ruby0.load-caches to warmup?
What exactly is saved when I do save-caches? just the addresses of data
stored inside the cache with the corresponding tag bits? or is the actual
data stored?
thx Mike.
On Tue, 24 Oct 2006, Mike Marty wrote:
See CacheMemory.h. You could just change printData() to call print()
which is implemented.
I forgot why this got implemented the way it did. I think printData() was
meant to dump out the raw data values, and that print() was meant to dump
the Entry information (states, etc)
--mike
I tried dumping cache state when running with both opal and ruby (using
the MOESI_CMP_directory protocol, and I get the following message in the
.cache file:
printData() not supported
Does the cache state printing only work for certain protocols?
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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!
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}