Hi Srini, You could have a separate clock domain for each core and each clock domain has its own clock period. Take a look at src/sim/clocked_object.hh . And I am no expert, so hopefully experienced users could provide more detailed info.
Thanks, Amin On Wed, Feb 5, 2014 at 12:23 AM, Srinivasan Narayanamoorthy < narayanam...@wisc.edu> wrote: > Hi,This is Srini. I have implemented a system level DFS in gem5 and it > seems to be working. Now I am trying to implement per-core DFS in gem5. > With the current class hierarchy, clockedObject is the parent of the cpu > classes and there is just one _clockPeriod member. Thus all cpu's update > the same _clockPeriod member and the clocks to the cpu change with every > core updating it. It would be really nice if some one can give any > suggestions on how to do per-core dfs. I am using a fairly recent revision > of gem5. When I checked some older versions(2012) I saw that the clock > period variable was part of the cpu class and hence per-core dfs would have > been straightforward. Please bear with me if I am naive. > > > Thanks > Srini > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
