| commit | 5faa7aaffd1767e91e0aa4049252473890275460 | [log] [tgz] |
|---|---|---|
| author | Tiago Mück <tiago.muck@arm.com> | Tue Mar 01 19:03:59 2022 -0600 |
| committer | Tiago Muck <tiago.muck@arm.com> | Wed Jun 01 15:23:47 2022 +0000 |
| tree | 0d1da05ab8feee4d1917478478a146d5c49d37ee | |
| parent | ff5aafa1e9e452061b7e63805ee1d611ed6ce9d9 [diff] |
mem-ruby: removed check for WriteCleanFull Relaxed check on Send_WriteCleanFull. That data state may actually happen if the writeback was triggered by a CleanUnique request. JIRA: https://gem5.atlassian.net/browse/GEM5-1195 Change-Id: I33ec5693df09efe39345f403c5b6d3388f1a5056 Signed-off-by: Tiago Mück <tiago.muck@arm.com> Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/57390 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Reviewed-by: Daecheol You <daecheol.you@samsung.com> Tested-by: kokoro <noreply+kokoro@google.com>
diff --git a/src/mem/ruby/protocol/chi/CHI-cache-actions.sm b/src/mem/ruby/protocol/chi/CHI-cache-actions.sm index 7dbb05c..6c87416 100644 --- a/src/mem/ruby/protocol/chi/CHI-cache-actions.sm +++ b/src/mem/ruby/protocol/chi/CHI-cache-actions.sm
@@ -1298,7 +1298,6 @@ assert(tbe.dataValid); assert(is_HN == false); assert(tbe.dataDirty); - assert(tbe.dataMaybeDirtyUpstream == false); enqueue(reqOutPort, CHIRequestMsg, request_latency) { prepareRequest(tbe, CHIRequestType:WriteCleanFull, out_msg);