Hi Joel, In the long term, I would suggest sticking to specifying the latency in cycles, especially if the module in questions might be subject to DVFS, i.e. We would use a relative metric rather than an absolute metric.
That said, for now you should be able to simply grab the parents clock parameter, which holds the clock period. Andreas On 23/08/2012 04:42, "Joel Hestness" <[email protected]> wrote: >Hey guys, > I'm trying to specify a latency parameter for an object in ns, but I >need >it converted to cycles of the parent object during Python parameter setup. > I'd like to grab the cycle period in ticks from the parent's Python clock >parameter to convert the ns value to number of cycles, so I don't have to >modify the C++ code of an existing gem5 object to pass in the ns >parameter. > Can someone recommend the best way to do this? > > Thanks, > Joel > > >-- > Joel Hestness > PhD Student, Computer Architecture > Dept. of Computer Science, University of Wisconsin - Madison > Dept. of Computer Science, University of Texas - Austin > http://www.cs.utexas.edu/~hestness >_______________________________________________ >gem5-dev mailing list >[email protected] >http://m5sim.org/mailman/listinfo/gem5-dev > -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
