diff options
| author | Nilay Vaish <nilay@cs.wisc.edu> | 2012-05-22 11:32:57 -0500 |
|---|---|---|
| committer | Nilay Vaish <nilay@cs.wisc.edu> | 2012-05-22 11:32:57 -0500 |
| commit | 6a966d5eeb2f73c5c3e48a7abe7db4a47902d121 (patch) | |
| tree | bc4981653de77935becf9cc0e6bc7536a91b2ddb | |
| parent | 4d4d212ae974b3a3ad6d185902d4896c0233a8d9 (diff) | |
| download | gem5-6a966d5eeb2f73c5c3e48a7abe7db4a47902d121.tar.xz | |
Ruby Sequencer: Schedule deadlock check event at correct time
The scheduling of the deadlock check event was being done incorrectly as the
clock was not being multiplied, so as to convert the time into ticks. This
patch removes that bug.
| -rw-r--r-- | src/mem/ruby/system/Sequencer.cc | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/mem/ruby/system/Sequencer.cc b/src/mem/ruby/system/Sequencer.cc index 4109a06fd..de7c8154b 100644 --- a/src/mem/ruby/system/Sequencer.cc +++ b/src/mem/ruby/system/Sequencer.cc @@ -220,7 +220,9 @@ Sequencer::insertRequest(PacketPtr pkt, RubyRequestType request_type) // See if we should schedule a deadlock check if (deadlockCheckEvent.scheduled() == false) { - schedule(deadlockCheckEvent, m_deadlock_threshold + curTick()); + schedule(deadlockCheckEvent, + m_deadlock_threshold * g_eventQueue_ptr->getClock() + + curTick()); } Address line_addr(pkt->getAddr()); |