Searched hist:11356 (Results 1 - 11 of 11) sorted by relevance
| /gem5/src/systemc/ext/core/ | ||
| H A D | sc_simcontext.hh | diff 12946:70c6625468c3 Mon Jun 18 22:09:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Enable some more sc_simcontext related tests. Now that we bit the bullet and stubbed out sc_simcontext and related functions a little bit, we can enable a couple more tests. This change also adds in some functions the new tests expect sc_simcontext to have. Change-Id: I00b5cc0c6eb658eb689b9c85ed171f290009768d Reviewed-on: https://gem5-review.googlesource.com/11356 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/systemc/core/ | ||
| H A D | sc_simcontext.cc | diff 12946:70c6625468c3 Mon Jun 18 22:09:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Enable some more sc_simcontext related tests. Now that we bit the bullet and stubbed out sc_simcontext and related functions a little bit, we can enable a couple more tests. This change also adds in some functions the new tests expect sc_simcontext to have. Change-Id: I00b5cc0c6eb658eb689b9c85ed171f290009768d Reviewed-on: https://gem5-review.googlesource.com/11356 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/ | ||
| H A D | simout | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| H A D | config.ini | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| H A D | stats.txt | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| /gem5/src/systemc/tests/ | ||
| H A D | working.filt | diff 12946:70c6625468c3 Mon Jun 18 22:09:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Enable some more sc_simcontext related tests. Now that we bit the bullet and stubbed out sc_simcontext and related functions a little bit, we can enable a couple more tests. This change also adds in some functions the new tests expect sc_simcontext to have. Change-Id: I00b5cc0c6eb658eb689b9c85ed171f290009768d Reviewed-on: https://gem5-review.googlesource.com/11356 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/tests/quick/fs/10.linux-boot/ref/arm/linux/realview-simple-timing-dual/ | ||
| H A D | stats.txt | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| /gem5/src/cpu/minor/ | ||
| H A D | lsq.cc | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| /gem5/src/cpu/o3/ | ||
| H A D | lsq_unit_impl.hh | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| /gem5/src/cpu/simple/ | ||
| H A D | timing.cc | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
| H A D | atomic.cc | diff 11356:a80884911971 Sun Jul 19 16:03:00 EDT 2015 Krishnendra Nathella <krinat01@arm.com> cpu: Fix LLSC atomic CPU wakeup Writes to locked memory addresses (LLSC) did not wake up the locking CPU. This can lead to deadlocks on multi-core runs. In AtomicSimpleCPU, recvAtomicSnoop was checking if the incoming packet was an invalidation (isInvalidate) and only then handled a locked snoop. But, writes are seen instead of invalidates when running without caches (fast-forward configurations). As as simple fix, now handleLockedSnoop is also called even if the incoming snoop packet are from writes. |
Completed in 179 milliseconds