diff options
author | Joel Hestness <jthestness@gmail.com> | 2013-04-09 16:25:30 -0500 |
---|---|---|
committer | Joel Hestness <jthestness@gmail.com> | 2013-04-09 16:25:30 -0500 |
commit | 1583056de8d5d9698cfeb87fb72a80e532e275c3 (patch) | |
tree | 0c20a636a5a3b030cbf89ee14919bc126e1411af /tests/quick/se/50.memtest/ref/alpha/linux | |
parent | 46d4b71aa244da24453d86184f3cf2ba8b5bdbac (diff) | |
download | gem5-1583056de8d5d9698cfeb87fb72a80e532e275c3.tar.xz |
Ruby: Fix RubyPort evict packet memory leak
When using the o3 or inorder CPUs with many Ruby protocols, the caches may
need to forward invalidations to the CPUs. The RubyPort was instantiating a
packet to be sent to the CPUs to signal the eviction, but the packets were
not being freed by the CPUs. Consistent with the classic memory model, stack
allocate the packet and heap allocate the request so on
ruby_eviction_callback() completion, the packet deconstructor is called, and
deletes the request (*Note: stack allocating the request causes double
deletion, since it will be deleted in the packet destructor). This results in
the least memory allocations without memory errors.
Diffstat (limited to 'tests/quick/se/50.memtest/ref/alpha/linux')
0 files changed, 0 insertions, 0 deletions