summaryrefslogtreecommitdiff
path: root/src/cpu/o3/probe/SimpleTrace.py
diff options
context:
space:
mode:
authorSteve Reinhardt <steve.reinhardt@amd.com>2016-01-17 18:27:46 -0800
committerSteve Reinhardt <steve.reinhardt@amd.com>2016-01-17 18:27:46 -0800
commite595d9cccb3c3a06f915547ecc9b224d65e7d5cc (patch)
tree89908ab023d996c83e32d925566ad564f3c88329 /src/cpu/o3/probe/SimpleTrace.py
parentfb0383bc72ba3621a69f5f4d0cebb65907f39cc0 (diff)
downloadgem5-e595d9cccb3c3a06f915547ecc9b224d65e7d5cc.tar.xz
arch: don't call *Timing functions from *Atomic versions
The readMemAtomic/writeMemAtomic helper functions were calling readMemTiming/writeMemTiming respectively. This is functionally correct, since the *Timing functions are doing the same access initiation operation as the *Atomic functions (just that the *Atomic versions also complete the access in line). It also provides for some (very minimal) code reuse. Unfortunately, it's potentially pretty confusing, since it makes it look like the atomic accesses are somehow being converted to timing accesses. It also gets in the way of specializing the timing interface (as will be done in a future patch).
Diffstat (limited to 'src/cpu/o3/probe/SimpleTrace.py')
0 files changed, 0 insertions, 0 deletions