On Wed, Mar 9, 2011 at 5:30 PM, Beckmann, Brad <brad.beckm...@amd.com>wrote:
> I believe the L1DcacheMemory is created right after system because inside > each protocol file the first thing attached to the system is the l1 > controllers. That way the controllers get a more descriptive name than what > they are as related to the topology. > > I'm still a little confused by the cycle error. If the parent.any call > searches the graph for the close object of that particular type, wouldn't > you always get a cycle using parent.any? Or are other uses of parent.any > more of an uncle search than a true parent search? > The cycle issue is just related to params... e.g., if the system object has the l1cache as a param, then the l1cache can't have the system as a param. Parent/child relationships by themselves don't directly factor into it. Steve _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
