Searched hist:8532 (Results 1 - 2 of 2) sorted by relevance
/gem5/src/mem/ruby/system/ | ||
H A D | RubyPort.cc | 8532:8f27cf8971fe Thu Sep 01 14:41:00 EDT 2011 Lisa Hsu <Lisa.Hsu@amd.com> Functional Accesses: Update states to support Broadcast/Snooping protocols. In the current implementation of Functional Accesses, it's very hard to implement broadcast or snooping protocols where the memory has no idea if it has exclusive access to a cache block or not. Without this knowledge, making sure the RW vs. RO permissions are right are next to impossible. So we add a new state called Backing_Store to enable the conveyance that this is the backup storage for a block, so that it can be written if it is the only possibly RW block in the system, or written even if there is another RW block in the system, without causing problems. Also, a small change to actually set the m_name field for each Controller so that debugging can be easier. Now you can access a controller's name just by controller->getName(). |
/gem5/src/mem/slicc/symbols/ | ||
H A D | StateMachine.py | 8532:8f27cf8971fe Thu Sep 01 14:41:00 EDT 2011 Lisa Hsu <Lisa.Hsu@amd.com> Functional Accesses: Update states to support Broadcast/Snooping protocols. In the current implementation of Functional Accesses, it's very hard to implement broadcast or snooping protocols where the memory has no idea if it has exclusive access to a cache block or not. Without this knowledge, making sure the RW vs. RO permissions are right are next to impossible. So we add a new state called Backing_Store to enable the conveyance that this is the backup storage for a block, so that it can be written if it is the only possibly RW block in the system, or written even if there is another RW block in the system, without causing problems. Also, a small change to actually set the m_name field for each Controller so that debugging can be easier. Now you can access a controller's name just by controller->getName(). |
Completed in 29 milliseconds