Re: [Gems-users] Simulated machine execution time

[Greg Byrd <gbyrd@xxxxxxxx>]

I tend to use the "sarek" configuration.  In $SIMICS/home/sarek/sarek-common.simics, there's a python variable "cpu_freq" that sets this parameter.  It defaults to 75.

Also, at least for the Ultrasparc processor, it's saved when you do a simics checkpoint.  Look for the string "freq_mhz".  You can just change this (for all processors) in the checkpoint file directly.

Note that changing this only affects time from the Simics point of view.  It doesn't have any effect on Ruby cycles.

...gb



pana wrote:

Hi, I'm interested in this topic, too.

On 10/23/07, Greg Byrd <gbyrd@xxxxxxxx> wrote:

The clock rate is set in the Simics description of the processor.  The
default, if I recall correctly, is 75 MHz.  (Yes, that seems low -- it's
set that way so that the console will be reasonable responsive to
keyboard events, etc.)

Does it depend on the starting configuration I choose, like "peanut"?
and which is the file shows me the current configuration?

Really, elapsed time in seconds is fairly meaningless -- you can simply
change the clock frequency to get whatever result you want!

...gb


Marco Solinas wrote:
> Hi list
>
> I need to know how long my simulation is, but I found only the
> "elapsed_time" and "virtual_time" in the stats file.
> The universal parameter is "Ruby_cycles", I need it in seconds.
>
> How can I calculate the execution time of the simulated machine?
> I think it has to be few seconds.
>
> Regards
> Marco
>
>

thanks a lot
bye

francesco

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