Searched hist:5046 (Results 1 - 10 of 10) sorted by relevance
/gem5/src/arch/x86/isa/ | ||
H A D | macroop.isa | diff 5046:da031ef02439 Wed Sep 05 02:32:00 EDT 2007 Gabe Black <gblack@eecs.umich.edu> X86: Add some SSE floating point/integer conversion microops. |
/gem5/src/mem/ | ||
H A D | coherent_xbar.hh | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
H A D | coherent_xbar.cc | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
H A D | packet.cc | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
H A D | request.hh | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
H A D | packet.hh | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
/gem5/src/arch/x86/isa/microops/ | ||
H A D | regop.isa | diff 5046:da031ef02439 Wed Sep 05 02:32:00 EDT 2007 Gabe Black <gblack@eecs.umich.edu> X86: Add some SSE floating point/integer conversion microops. |
/gem5/src/arch/x86/isa/decoder/ | ||
H A D | two_byte_opcodes.isa | diff 5046:da031ef02439 Wed Sep 05 02:32:00 EDT 2007 Gabe Black <gblack@eecs.umich.edu> X86: Add some SSE floating point/integer conversion microops. |
/gem5/src/mem/cache/ | ||
H A D | cache.hh | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
H A D | cache.cc | diff 12346:9b1144d046ca Thu Sep 22 05:07:00 EDT 2016 Nikos Nikoleris <nikos.nikoleris@arm.com> mem: Support for specifying the destination of a WriteClean Previously, WriteClean packets would always write to the first memory below unless the memory was unable to allocate in which case it would be forwarded further below. This change adds support for specifying the destination of a WriteClean packet. The cache annotates the request with the specified destination and marks the packet as write-through upon its creation. The coherent xbar checks packets for their destination and resets the write-through flag when necessary e.g., the coherent xbar that is set as the PoC will reset the write-through flag for packets to the PoC. Change-Id: I84b653f5cb6e46e97e09508649a3725d72d94606 Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Anouk Van Laer <anouk.vanlaer@arm.com> Reviewed-on: https://gem5-review.googlesource.com/5046 Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
Completed in 219 milliseconds