mem: Always use SenderState for response routing in RubyPort
Review Request #2597 - Created Jan. 5, 2015 and submitted
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 10645:feaa007b5faf --------------------------- 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.
Posted (Jan. 15, 2015, 5:49 a.m.)
-
src/mem/ruby/system/RubyPort.cc (Diff revision 1) -
Why move this print statement? This change might cause merge conflicts when people pull updates.
Posted (Jan. 15, 2015, 5:53 a.m.)
-
src/mem/ruby/system/RubyPort.cc (Diff revision 1) -
The statement is changed and uses the port which we only know after getting it from the sender state.