Hi All,
I have more patches that I would like everyone to review. I haven't yet received any feedback on my last set of patches, so I'm going to hold off on pushing them before Christmas. For those of you who haven't had a chance yet to review the previous set, you can review both sets at your leisure over the next couple of weeks. I, like I'm sure many others, will be on vacation thru 1/3. For this new set of patches, I'm particularly interested to receive feedback from the Wisconsin folks on my patch entitled "ruby: Cleaned up static members in RubyPort". The patch removes the static hit callback function and uniquely id ruby requests. I don't plan to check this patch in as is because it will likely break ruby's atomic support and key libruby APIs. However, I would be interested to know if the people at Wisconsin feel that they can work with some of the changes this patch makes. Can we remove the atomic support's need to overload the request id? Can libruby use a per RubyPort method instead of a global function? Etc... The other major change in this new set of patches is I've resurrected the old Ruby tester and made it a cpu MemObject, similar to the memtester. The Ruby tester still needs to test atomics, dma accesses, and work with M5 data rather than the ruby SubBlock object. I'll make sure to this before I check it in. I look forward to your comments and suggestions. Happy Holidays. Brad
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
