> The idea with Parent is that you would go into the icache and dcache, and > in each of those say: > > self.clock = Parent.clock > > which would set their clock parameters to a proxy object that will wait > until instantiation, then search up the hierarchy for the nearest enclosing > object's clock value.
Andreas, I believe that I also sent you code that would turn '2c' into 2 * Parent.clock. Furthermore, I brought this up a month ago: > I agree. To me, the right solution is to bind the proxy even later. > Don't bind it in Python, but rather in C++ so that we can re-bind it > in the future. Essentially a clocked object has a period parameter > and a parent pointer. If the parent is NULL (no parent), then the > concrete period is an absolute period in ticks. If the parent is > non-null, then the concrete period is the period parameter multiplied > by the parent ticks. If ClockedObjects also had a list of children, > then we could traverse the tree of clocked objects any time a clock > period was changed and thus be able to deal with DVFS (and the general > notion of clock domains) more easily. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
