From fc3d34a4889f96395d7d3185a0c5a2dbb5c77343 Mon Sep 17 00:00:00 2001 From: Nilay Vaish Date: Thu, 27 Aug 2015 12:51:40 -0500 Subject: ruby: handle llsc accesses through CacheEntry, not CacheMemory The sequencer takes care of llsc accesses by calling upon functions from the CacheMemory. This is unnecessary once the required CacheEntry object is available. Thus some of the calls to findTagInSet() are avoided. --- src/mem/ruby/structures/CacheMemory.hh | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/mem/ruby/structures/CacheMemory.hh') diff --git a/src/mem/ruby/structures/CacheMemory.hh b/src/mem/ruby/structures/CacheMemory.hh index 08551ab87..6c719cb4f 100644 --- a/src/mem/ruby/structures/CacheMemory.hh +++ b/src/mem/ruby/structures/CacheMemory.hh @@ -107,6 +107,11 @@ class CacheMemory : public SimObject // Set this address to most recently used void setMRU(Addr address); + // Functions for locking and unlocking cache lines corresponding to the + // provided address. These are required for supporting atomic memory + // accesses. These are to be used when only the address of the cache entry + // is available. In case the entry itself is available. use the functions + // provided by the AbstractCacheEntry class. void setLocked (Addr addr, int context); void clearLocked (Addr addr); bool isLocked (Addr addr, int context); -- cgit v1.2.3