Searched hist:11139 (Results 1 - 7 of 7) sorted by relevance
/gem5/src/mem/probes/ | ||
H A D | base.hh | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
H A D | stack_dist.hh | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
H A D | stack_dist.cc | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
H A D | mem_trace.cc | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
H A D | mem_trace.hh | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
/gem5/src/sim/probe/ | ||
H A D | mem.hh | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
/gem5/src/mem/ | ||
H A D | comm_monitor.cc | diff 11139:bd894d2bdd7c Fri Sep 25 13:25:00 EDT 2015 Andreas Hansson <andreas.hansson@arm.com> mem: Add PacketInfo to be used for packet probe points This patch fixes a use-after-delete issue in the packet probe points by adding a PacketInfo struct to retain the key fields before passing the packet onwards. We want to probe the packet after it is successfully sent, but by that time the fields may be modified, and the packet may even be deleted. Amazingly enough the issue has gone undetected for months, and only recently popped up in our regressions. |
Completed in 47 milliseconds