Hi Daecheol, I agree with you, m_stall_time calculation does not make much sens to me either. It is unreliable at best if you just look at its variations from one run to the next. And looking at it again, I think it is even bugged since the default copy constructor for Message has been added (m_time is not updated upon copy).
I think that a distribution stat would be the most natural representation for message "stall time". The biggest drawback is that you need to specify a min and max value for the distribution. Everything below (resp. above) this range will be stored in a single "bellow min" (resp. "above max") bucket. Min obviously is 0 for "stall times" but max is harder to define in general, especially if changing the tick frequency. As a rule of thumb, I would define max slightly above the highest value you consider acceptable. Maybe add a MessageBuffer parameter to be able to specify it from the python script. Best, Gabriel _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
