mem-ruby: fix Sequencer latency reporting
authorTiago Mück <tiago.muck@arm.com>
Thu, 1 Oct 2020 21:45:56 +0000 (16:45 -0500)
committerTiago Mück <tiago.muck@arm.com>
Thu, 11 Feb 2021 17:12:22 +0000 (17:12 +0000)
commit1861bc39ea460f5509367919b000c1c492c4d184
tree17f053576556f9d3965f6e4bfd6a000c7e563d7c
parentc1cb1f2f936603b9b3efdb38b952c105b75b3650
mem-ruby: fix Sequencer latency reporting

Most protocols won't set initialRequestTime, forwardRequestTime, and
firstResponseTime, thus leading to calculated latency being always 0.

Change-Id: Id2c73314a964bf6efb262d40b3df515373023b84
Signed-off-by: Tiago Mück <tiago.muck@arm.com>
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/41114
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
src/mem/ruby/system/Sequencer.cc