----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3470/#review8324 -----------------------------------------------------------
The description still needs to be fixed. It should follow this form: gpu-compute: summary description Also, this is not a VIPER specific bug, it's a bug in the way the global pipeline handles these counts. - Tony Gutierrez On May 18, 2016, 3:58 p.m., Tuan Ta wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/3470/ > ----------------------------------------------------------- > > (Updated May 18, 2016, 3:58 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > gpu-compute: In VIPER protocol, inflighStores should not be incremented for > memory fence instruction. Deadlock could happen when there are many fence > instructions executed by a compute unit because inflightStores will > eventually go over gmQueueSize. > > > Diffs > ----- > > src/gpu-compute/global_memory_pipeline.cc 54cf9a388a9d > > Diff: http://reviews.gem5.org/r/3470/diff/ > > > Testing > ------- > > > Thanks, > > Tuan Ta > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
