Searched hist:581 (Results 1 - 7 of 7) sorted by relevance
| /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 163 milliseconds