Hi,
This question is mostly for Derek, but I figured that others at Wisconsin may be able to answer it as well. I notice that the current Ruby atomic support requires the sequencer to have direct access to its associated L1 cache controller, rather than just via the mandatory queue. Derek recently told me that he has some changes to how atomics are supported in Ruby. Does that new atomic support also require the sequencer to have a pointer to the cache controller? The reason I ask is it impacts the new unified configuration support. We can make it work as is, I just wanted to confirm that the effort was worth it. Thanks, Brad
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
