On Tue, 29 Mar 2011, Nilay Vaish wrote:
Brad, I have posted on the review board my current implementation for
supporting functional accesses in Ruby. This is untested and is mainly meant
for furthering the discussions. I have some questions for you --
1. How do we inform the other end of RubyPort's M5 Port about whether or not
functional access was successful?
2. What's the role of directory memory in functional accesses?
3. If none of the caches have the block pertaining to the address of the
access, then read accesses should be satisfied from the physical memory.
Write accesses should always go to physical memory as well. How can physical
memory be accessed from RubyPort?
--
Nilay
Brad, I have made some changes to the patch. I have updated it on the
review board. I have added a call to sendFunctional() so as to send the
response. I have also added call to sendFunctional() on the physical
memory port of ruby port, so that the physical memory would also get
updated.
You had mentioned that we would unhook M5 memory and use Ruby to supply
the data. How do we do this? And the second question from the previous
mail still remains unanswered.
Thanks
Nilay
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
