> If you want a system where concurrently running partitions of SimObjects > only communicate through events and you demand that those events only affect > one target object (so it can't have any references other then the one to the > target SimObject) then this is not a problem. This is one of the > restrictions I would like in a mandatory interface between concurrently > running objects. If you want a 100% safe execution of a certain > configuration script then this restriction should be checked and enforced > for every configuration script. In other words, concurrently running > partitions of SimObjects should only communicate through such an interface.
At first I was thinking of Request objects, but they're not reference counted. EtherPacket and StaticInst however are both things that I could envision living in multiple threads simultaneously. Both could just be explicitly copied when moving from one thread to another. StaticInst maybe should not even be reference counted since the objects are just kept around forever in the decode cache anyway. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
