[ Resending to m5-dev, oops to the other list --nate ] I need to add some stuff to the sendStatusChange idea, but the way it is currently designed isn't that useful to me. I was thinking that we should change the interface to something like sendInfoRequest, and use RTTI to specify what is sent. We could fold requests for block size, range change, and address range into this mechanism, and it would give me an easy way to send out other types of requests across my network simulation.
It seems to me that the printAddr mechanism that Steve did could also be folded into this mechanism as well (instead of hijacking sendFunctional). Maybe this one is going too far, but for the other ones, I don't see a good reason not to do this. One thing that is interesting no matter what we choose is what to do when an object doesn't know about an information request type. Should we just pass the request through the object (and broadcast it in the case of networks/busses), or should we error out? What do you all think? I'm hoping that Steve at least will reply. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
