From 8877516e5b4f1195d4e0f8ef0789057f14347e80 Mon Sep 17 00:00:00 2001
From: Vishnu Ramadas <vramadas@outlook.com>
Date: Fri, 6 Dec 2024 18:45:23 -0600
Subject: [PATCH] mem-ruby: Fix GPU_VIPER-TCP.sm atomic transitions in TCC WB
 mode

The transition that happens when TCC acknowledges TCP of an atomic
operation completion does not move the cacheline state from A to I. This
commit fixes the transition and moves the state to I
---
 src/mem/ruby/protocol/GPU_VIPER-TCP.sm | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/src/mem/ruby/protocol/GPU_VIPER-TCP.sm b/src/mem/ruby/protocol/GPU_VIPER-TCP.sm
index f69fe33aff..a9f3169605 100644
--- a/src/mem/ruby/protocol/GPU_VIPER-TCP.sm
+++ b/src/mem/ruby/protocol/GPU_VIPER-TCP.sm
@@ -917,11 +917,21 @@ machine(MachineType:TCP, "GPU TCP (L1 Data Cache)")
   // store followed by a load. Thus, complete the store without affecting
   // TBE or line state.
   // TCC_AckWB only snoops TBE
-  transition({V, I, IV, A}, TCC_AckWB) {
+  transition({V, I, IV}, TCC_AckWB) {
     wd_wtDone;
     pr_popResponseQueue;
   }
 
+  transition(A, TCC_AckWB, I) {TagArrayRead, DataArrayRead, DataArrayWrite} {
+    a_allocate;
+    w_writeCache;
+    ad_atomicDone;
+    ic_invCache;
+    wada_wakeUpAllDependentsAddr;
+    d_deallocateTBE;
+    pr_popResponseQueue;
+  }
+
   transition(F, TCC_AckWB, I) {
     f_flushDone;
     pr_popResponseQueue;