summaryrefslogtreecommitdiff
path: root/src/mem/ruby/buffers/MessageBuffer.hh
diff options
context:
space:
mode:
authorNilay Vaish <nilay@cs.wisc.edu>2013-03-22 17:21:22 -0500
committerNilay Vaish <nilay@cs.wisc.edu>2013-03-22 17:21:22 -0500
commite85b556d705c3045f7fa8cba3a9a6a4039bc18e7 (patch)
tree71c1a121f050dd0f23c80421089b40aa583afb78 /src/mem/ruby/buffers/MessageBuffer.hh
parent47c8cb72fc0b400326c7b9b1f82542d4b72295bd (diff)
downloadgem5-e85b556d705c3045f7fa8cba3a9a6a4039bc18e7.tar.xz
ruby: message buffer: correct previous errors
A recent set of patches added support for multiple clock domains to ruby. I had made some errors while writing those patches. The sender was using the receiver side clock while enqueuing a message in the buffer. Those errors became visible while creating (or restoring from) checkpoints. The errors also become visible when a multi eventq scenario occurs.
Diffstat (limited to 'src/mem/ruby/buffers/MessageBuffer.hh')
-rw-r--r--src/mem/ruby/buffers/MessageBuffer.hh2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mem/ruby/buffers/MessageBuffer.hh b/src/mem/ruby/buffers/MessageBuffer.hh
index 01bbcb525..ae1635b69 100644
--- a/src/mem/ruby/buffers/MessageBuffer.hh
+++ b/src/mem/ruby/buffers/MessageBuffer.hh
@@ -210,7 +210,7 @@ class MessageBuffer
bool m_ordering_set;
bool m_randomization;
- Cycles m_last_arrival_time;
+ Tick m_last_arrival_time;
int m_input_link_id;
int m_vnet_id;