Searched hist:10821 (Results 1 - 8 of 8) sorted by relevance
| /gem5/src/systemc/ | ||
| H A D | SConsopts | 12817:e634213487cd Tue May 01 20:50:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Add a stubbed out sc_object class. Also add a SConsopt variable USE_SYSTEMC to hide systemc support until it's usable. Change-Id: Ibb37483432b147ee690a36bb5c8dd74f1c4c7ae4 Reviewed-on: https://gem5-review.googlesource.com/10821 Reviewed-by: Giacomo Travaglini <giacomo.travaglini@arm.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/dev/ | ||
| H A D | dma_device.cc | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
| /gem5/src/mem/ | ||
| H A D | snoop_filter.cc | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
| H A D | coherent_xbar.cc | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
| /gem5/src/mem/cache/ | ||
| H A D | mshr.cc | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
| H A D | base.hh | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
| H A D | base.cc | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
| /gem5/src/cpu/o3/ | ||
| H A D | cpu.cc | 10821:581fb2484bd6 Tue May 05 03:22:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Snoop into caches on uncacheable accesses This patch takes a last step in fixing issues related to uncacheable accesses. We do not separate uncacheable memory from uncacheable devices, and in cases where it is really memory, there are valid scenarios where we need to snoop since we do not support cache maintenance instructions (yet). On snooping an uncacheable access we thus provide data if possible. In essence this makes uncacheable accesses IO coherent. The snoop filter is also queried to steer the snoops, but not updated since the uncacheable accesses do not allocate a block. |
Completed in 155 milliseconds