> >> 1) Having a scalar "clock" is not the solution and the clocked objects (what >> ever they are) should rather have a pointer to a clock object or a clock >> domain? > > Until you implement DVFS, I see no reason to write this code. You can > do things like "5 * Parent.clock.frequency" if you want to get a clock > multiplier. Adding this now will just overcomplicate the change with > something that is relatively orthogonal and should be in a separate > commit anyway. > > I still think that the ClockedObject is a useful concept. Not all > things that use a clock will always be MemObjects.
I think getting DVFS (really its just frequency scaling) implemented is pretty high on my list, so I'd like to make sure that it if any changes are made, that is a consideration. If you have the clock scaling via an object part implemented, implementing dvfs is as simple as filling in the appropriate register that he cpu can write to which changes the clock frequency. Ali _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
