)]}' { "commit": "f876e60bc264ab05cd49a1f444460bdbd5fd05fe", "tree": "065174a60f0d58a318c4e84fc9519387eea37530", "parents": [ "8e150924cbabfda5267b2bca21ddf3701c86f198" ], "author": { "name": "Kyle Roarty", "email": "kyleroarty1716@gmail.com", "time": "Wed May 04 14:46:57 2022 -0500" }, "committer": { "name": "Bobby Bruce", "email": "bbruce@ucdavis.edu", "time": "Mon Jun 06 18:28:52 2022 +0000" }, "message": "mem-ruby: Fix deadlock in GPU VIPER TCC\n\nA deadlock occured where we got a RdBlk while in W,\nwhich put us in WI while we wait for a writeback to complete.\n\nThis would cause the request to be stalled while the writeback\nwas occuring, but when the writeback completed (WBAck), we never\nwoke up the requests and thus never completed the RdBlk.\n\nThis commit adds a wakeup when we receive a WBAck while in WI.\n\nChange-Id: I01edf1d7a47757b4f680baf9f33a1a6aa37e7e25\nReviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/59352\nReviewed-by: Matt Sinclair \u003cmattdsinclair@gmail.com\u003e\nMaintainer: Matt Sinclair \u003cmattdsinclair@gmail.com\u003e\nReviewed-by: Matthew Poremba \u003cmatthew.poremba@amd.com\u003e\nTested-by: kokoro \u003cnoreply+kokoro@google.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "0d925654b119bc2778b83fc1c906ff54fdd0f35b", "old_mode": 33188, "old_path": "src/mem/ruby/protocol/GPU_VIPER-TCC.sm", "new_id": "032a64cec4230ad1885f21d3e4f85167b8081149", "new_mode": 33188, "new_path": "src/mem/ruby/protocol/GPU_VIPER-TCC.sm" } ] }