From 00536b0efc6d437fdf0cc0374b818b27ba32d217 Mon Sep 17 00:00:00 2001 From: Andreas Hansson Date: Thu, 22 Jan 2015 05:01:24 -0500 Subject: mem: Always use SenderState for response routing in RubyPort This patch aligns how the response routing is done in the RubyPort, using the SenderState for both memory and I/O accesses. Before this patch, only the I/O used the SenderState, whereas the memory accesses relied on the src field in the packet. With this patch we shift to using SenderState in both cases, thus not relying on the src field any longer. --- src/mem/ruby/system/Sequencer.cc | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/mem/ruby/system/Sequencer.cc') diff --git a/src/mem/ruby/system/Sequencer.cc b/src/mem/ruby/system/Sequencer.cc index ef1b9676b..dbf350199 100644 --- a/src/mem/ruby/system/Sequencer.cc +++ b/src/mem/ruby/system/Sequencer.cc @@ -547,6 +547,8 @@ Sequencer::hitCallback(SequencerRequest* srequest, DataBlock& data, // subBlock with the recieved data. The tester will later access // this state. if (m_usingRubyTester) { + DPRINTF(RubySequencer, "hitCallback %s 0x%x using RubyTester\n", + pkt->cmdString(), pkt->getAddr()); RubyTester::SenderState* testerSenderState = pkt->findNextSenderState(); assert(testerSenderState); -- cgit v1.2.3