diff options
| author | Korey Sewell <ksewell@umich.edu> | 2011-06-19 21:43:41 -0400 |
|---|---|---|
| committer | Korey Sewell <ksewell@umich.edu> | 2011-06-19 21:43:41 -0400 |
| commit | 5ef0b7a9db3c6ec4ca191c2e9381719e1e694873 (patch) | |
| tree | 718fdaf81b288b91bbac7eb2a8bae285d2dc39ac /src/cpu/thread_context.hh | |
| parent | 716e447da8424386f2c3448c17891927aeb49f67 (diff) | |
| download | gem5-5ef0b7a9db3c6ec4ca191c2e9381719e1e694873.tar.xz | |
inorder/dtb: make sure DTB translate correct address
The DTB expects the correct PC in the ThreadContext
but how if the memory accesses are speculative? Shouldn't
we send along the requestor's PC to the translate functions?
Diffstat (limited to 'src/cpu/thread_context.hh')
0 files changed, 0 insertions, 0 deletions