cabd4768c7
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.
14 lines
831 B
Text
Executable file
14 lines
831 B
Text
Executable file
gem5 Simulator System. http://gem5.org
|
|
gem5 is copyrighted software; use the --copyright option for details.
|
|
|
|
gem5 compiled Feb 29 2016 18:59:12
|
|
gem5 started Feb 29 2016 18:59:20
|
|
gem5 executing on redacted.arm.com, pid 18325
|
|
command line: build/ALPHA/gem5.opt -d build/ALPHA/tests/opt/quick/fs/10.linux-boot/alpha/linux/tsunami-simple-timing-dual -re /z/atgutier/gem5/gem5-commit/tests/run.py build/ALPHA/tests/opt/quick/fs/10.linux-boot/alpha/linux/tsunami-simple-timing-dual
|
|
|
|
Global frequency set at 1000000000000 ticks per second
|
|
info: kernel located at: /dist/m5/system/binaries/vmlinux
|
|
0: system.tsunami.io.rtc: Real-time clock set to Thu Jan 1 00:00:00 2009
|
|
info: Entering event queue @ 0. Starting simulation...
|
|
info: Launching CPU 1 @ 881785000
|
|
Exiting @ tick 1982592736000 because m5_exit instruction encountered
|