I have continued trying to understand how gem5 manage a writeback, but I am block in one function.
The chain of calls is this, recvTimingReq (CacheImpl.hh) -> allocateWriteBuffer (base.hh) -> allocateBufferInternal (base.hh) -> allocate (mshr.hh) -> add (TargetList in mshr.hh) -> push_back (???) My problem is that a call to push_back is defined, but I don't understand where is defined this push_back. I also tried to follow the inheritance chain but I went nowhere. My doubt is how the writeback is written in the next memory level, it should not be a normal access who call the accessBlock method, defined in the replacement policy, because writesbacks are out from the critical path. I need to change the cache state after a writeback. Thanks in advance Rodrigo From: [email protected] To: [email protected] Date: Thu, 2 May 2013 15:00:18 +0000 Subject: [gem5-users] Writeback detection Hello everyone, I am working with cache replacement policies using the classic model, I need to manage what happens with writebacks. I followed the writebacks chain from recvTimingReq (CacheImpl.hh), allocateWriteBuffer (base.hh), allocateBufferInternar (base.hh) to allocate (MSHR). My problem is that seems that the cache replacement policy defined in tags is not used when a writeback. Is it right? Thanks in advance Rodrigo _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
