derek/gem5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mem-ruby: Fix functional access in MI_example (#1838)

Browse Source 
In MI_example, when in MI state the block "Maybe_Stale" as in this
controller may have the most up to date value or it could be in the
network. For MII it is guaranteed that this controller has the most up
to date value because it received a PUTX_NACK.

This fixes one of the daily test failures.
This commit is contained in:
Jason Lowe-Power
2024-12-04 23:50:21 -05:00
committed by Bobby R. Bruce
parent a8db1fc683
commit 5672d63ae4
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/mem/ruby/protocol/MI_example-cache.sm
View File

@@ -52,8 +52,8 @@ machine(MachineType:L1Cache, "MI Example L1 Cache")
I, AccessPermission:Invalid, desc="Not Present/Invalid";
II, AccessPermission:Busy, desc="Not Present/Invalid, issued PUT";
M, AccessPermission:Read_Write, desc="Modified";
MI, AccessPermission:Busy, desc="Modified, issued PUT";
MII, AccessPermission:Busy, desc="Modified, issued PUTX, received nack";
MI, AccessPermission:Maybe_Stale, desc="Modified, issued PUT";
MII, AccessPermission:Read_Write, desc="Modified, issued PUTX, received nack";
IS, AccessPermission:Busy, desc="Issued request for LOAD/IFETCH";
IM, AccessPermission:Busy, desc="Issued request for STORE/ATOMIC";