mem: Always use SenderState for response routing in RubyPort
authorAndreas Hansson <andreas.hansson@arm.com>
Thu, 22 Jan 2015 10:01:24 +0000 (05:01 -0500)
committerAndreas Hansson <andreas.hansson@arm.com>
Thu, 22 Jan 2015 10:01:24 +0000 (05:01 -0500)
commit00536b0efc6d437fdf0cc0374b818b27ba32d217
tree9a9eeb74a20a63cd91ecbf200f49b9f473151e34
parent072f78471d11c31b6009beb572296f704912d0f7
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/RubyPort.cc
src/mem/ruby/system/Sequencer.cc