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.
This commit is contained in:
@@ -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());
|
||||
|
||||
Reference in New Issue
Block a user