sanchayanmaity/gem5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

config: Update memtest to stress test clean writebacks

Browse source 
This patch adds yet another twist to the memtest cache hierarchy, in that
the writeback_clean option is toggled at every level to match the
clusivity of the downstream cache.
This commit is contained in:
Andreas Hansson 2015-11-06 03:26:44 -05:00
parent 7433d77fcf
commit 337774e192
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
configs/example/memtest.py
View file

@ -177,7 +177,8 @@ else:
# Define a prototype L1 cache that we scale for all successive levels # Define a prototype L1 cache that we scale for all successive levels
proto_l1 = Cache(size = '32kB', assoc = 4, proto_l1 = Cache(size = '32kB', assoc = 4,
hit_latency = 1, response_latency = 1, hit_latency = 1, response_latency = 1,
tgts_per_mshr = 8, clusivity = 'mostly_incl') tgts_per_mshr = 8, clusivity = 'mostly_incl',
writeback_clean = True)
if options.blocking: if options.blocking:
proto_l1.mshrs = 1 proto_l1.mshrs = 1
@ -201,6 +202,7 @@ for scale in cachespec[:-1]:
# Swap the inclusivity/exclusivity at each level. L2 is mostly # Swap the inclusivity/exclusivity at each level. L2 is mostly
# exclusive with respect to L1, L3 mostly inclusive, L4 mostly # exclusive with respect to L1, L3 mostly inclusive, L4 mostly
# exclusive etc. # exclusive etc.
next.writeback_clean = not prev.writeback_clean
if (prev.clusivity.value == 'mostly_incl'): if (prev.clusivity.value == 'mostly_incl'):
next.clusivity = 'mostly_excl' next.clusivity = 'mostly_excl'
else: else: