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
On Tue, 29 Mar 2011, Nilay Vaish wrote:
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/611/
-----------------------------------------------------------
Review request for Default.
Summary
-------
Ruby: Add support for functional accesses
This patch is meant for aiding discussions on implementation of functional
access support in Ruby.
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev