Searched hist:11798 (Results 1 - 4 of 4) sorted by relevance
| /gem5/util/tlm/examples/master_port/ | ||
| H A D | main.cc | diff 11822:9018cadf6c87 Thu Feb 09 19:15:00 EST 2017 Christian Menard <Christian.Menard@tu-dresden.de> misc: Clean up and complete the gem5<->SystemC-TLM bridge [5/10] Changeset 11798:3a490c57058d --------------------------- misc: Clean up and complete the gem5<->SystemC-TLM bridge [5/10] The current TLM bridge only provides a Slave Port that allows the gem5 world to send request to the SystemC world. This patch series refractors and cleans up the existing code, and adds a Master Port that allows the SystemC world to send requests to the gem5 world. This patch: * Introduce transactor modules that represent the gem5 ports in the * SystemC world. * Update the SimControl module and let it keep track of the gem5 ports. Reviewed at http://reviews.gem5.org/r/3775/ Signed-off-by: Jason Lowe-Power <jason@lowepower.com> |
| /gem5/util/tlm/examples/slave_port/ | ||
| H A D | main.cc | diff 11822:9018cadf6c87 Thu Feb 09 19:15:00 EST 2017 Christian Menard <Christian.Menard@tu-dresden.de> misc: Clean up and complete the gem5<->SystemC-TLM bridge [5/10] Changeset 11798:3a490c57058d --------------------------- misc: Clean up and complete the gem5<->SystemC-TLM bridge [5/10] The current TLM bridge only provides a Slave Port that allows the gem5 world to send request to the SystemC world. This patch series refractors and cleans up the existing code, and adds a Master Port that allows the SystemC world to send requests to the gem5 world. This patch: * Introduce transactor modules that represent the gem5 ports in the * SystemC world. * Update the SimControl module and let it keep track of the gem5 ports. Reviewed at http://reviews.gem5.org/r/3775/ Signed-off-by: Jason Lowe-Power <jason@lowepower.com> |
| /gem5/src/mem/ruby/profiler/ | ||
| H A D | Profiler.cc | diff 11798:e034a4566653 Thu Jan 19 11:59:00 EST 2017 Tony Gutierrez <anthony.gutierrez@amd.com> ruby: guard usage of GPUCoalescer code in Profiler the GPUCoalescer code is used in the ruby profiler regardless of whether or not the coalescer code has been compiled, which can lead to link/run time errors. here we add #ifdefs to guard the usage of GPUCoalescer code. eventually we should refactor this code to use probe points. |
| /gem5/ | ||
| H A D | SConstruct | diff 11798:e034a4566653 Thu Jan 19 11:59:00 EST 2017 Tony Gutierrez <anthony.gutierrez@amd.com> ruby: guard usage of GPUCoalescer code in Profiler the GPUCoalescer code is used in the ruby profiler regardless of whether or not the coalescer code has been compiled, which can lead to link/run time errors. here we add #ifdefs to guard the usage of GPUCoalescer code. eventually we should refactor this code to use probe points. |
Completed in 78 milliseconds