From: Daniel R. Carvalho Date: Mon, 5 Mar 2018 15:06:21 +0000 (+0100) Subject: mem-cache: Use findBlock() in accessBlock() X-Git-Tag: v19.0.0.0~2264 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=a66fe6a8c36c9ab49cb3a35065bfc645d51036c8;p=gem5.git mem-cache: Use findBlock() in accessBlock() Use placement policy specific block search within generic access. Change-Id: I6070035e6e00595bcf073d4011f78a55ba7e7a8a Reviewed-on: https://gem5-review.googlesource.com/8721 Reviewed-by: Nikos Nikoleris Maintainer: Nikos Nikoleris --- diff --git a/src/mem/cache/tags/base_set_assoc.hh b/src/mem/cache/tags/base_set_assoc.hh index fc15b0220..21a250e75 100644 --- a/src/mem/cache/tags/base_set_assoc.hh +++ b/src/mem/cache/tags/base_set_assoc.hh @@ -161,9 +161,7 @@ public: */ CacheBlk* accessBlock(Addr addr, bool is_secure, Cycles &lat) override { - Addr tag = extractTag(addr); - int set = extractSet(addr); - BlkType *blk = sets[set].findBlk(tag, is_secure); + BlkType *blk = findBlock(addr, is_secure); // Access all tags in parallel, hence one in each way. The data side // either accesses all blocks in parallel, or one block sequentially on