Hey guys, I've been trying to update to the latest gem5 for gem5-gpu, and I'm getting all kinds of warnings about clock domains because of the way they are handled currently. In particular, clock domains are attached as children of the SimObjects that represent a part of the processor's functionality (e.g. cpu cores have a child clock domain), but often in system configuration files, you need to hang onto the clock domain by attaching as a child of, say, the system that you're instantiating. This leads to warnings that the clock domain already has a parent (both SimObjects and the system).
This seems really backwards to me. I think that clock domains should be managed by the top-level system, and other components in the system should be added as children of the clock domains, especially since we've also introduced derived clocks, which make the whole object hierarchy even messier when they are children of SimObjects and the parent clock domain. Is there a particular reason why this was inverted? If not, I think we should aim to make clock domains the parents of all the processor component SimObjects. Thanks, Joel -- Joel Hestness PhD Student, Computer Architecture Dept. of Computer Science, University of Wisconsin - Madison http://pages.cs.wisc.edu/~hestness/ _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
