Read after write fails

[PhilippKasgen]

Read after write check fails in MESI Inclusive

Detailed description of problem or enhancement

We ported gem5's RubyTester to SST and call this SST component "memHierarchyTester". It randomly reads from and writes to a tight address space but it behaves like multiple cores, i.e. it has multiple L1 cache ports. During these tests, it will also check whether it can read back the same value it has previously written (possibly from another "core"). When running the configuration in the attached out.txt, this check fails. We suspect a bug in the MESI protocol. Can you reproduce this error? (I had to rename the .json file as .txt because otherwise github wouldn't allow uploading it.)

Thank you in advance!

Describe how to reproduce

git clone https://github.com/PhilippKasgen/sst-elements
cd sst-elements
git checkout memHierarchyTester
...

Download out.txt rename it to out.json

sst out.json

Output dump should contain this line among others: FATAL: MemHierarchyTester[performCallback:292]: Action/check failure: proc: 2749 at address: 464, byte_number: 0, the expected value is 59 but received 99 instead. Time: 5031025

sst repositories

sst-core: v12.0.1_Final sst-elements-fork: branch memHierarchyTester (based on v12.0.1_Final)