Thank you very much. I will give Ruby a try. Am Freitag, 7. August 2020,
16:41:12 MESZ hat Ciro Santilli <ciro.santi...@arm.com> Folgendes geschrieben:
#yiv9784044512 P {margin-top:0;margin-bottom:0;}It might be the same as:
https://gem5.atlassian.net/browse/GEM5-711 I want to investigate that soon
hopefully.
If you try Ruby and it fails, please open a separate bug, we want it to work as
well🙂From: Sebastian Block via gem5-users <gem5-users@gem5.org>
Sent: Friday, August 7, 2020 9:27 AM
To: gem5-users@gem5.org <gem5-users@gem5.org>
Cc: Sebastian Block <seb.block...@yahoo.de>
Subject: [gem5-users] Error only occurs with higher number of clusters and cpus
Hi all,
My gem5 project consists of clusters and some cpus in the clusters, simulating
them in fs mode.Simulating in atomic mode always works. While simulating less
then 6 cpus works perfectly fine in timing mode, with more then 6 the
simulation crashes with the error: ----
panic: panic condition (pkt->needsWritable() != pkt->isInvalidate()) &&
!pkt->req->isCacheMaintenance() occurred: global got snoop WriteReq
[80a70800:80a70803] UC where needsWritable, does not match isInvalidateMemory
Usage: 9072952 KBytesProgram aborted at tick 175141645000--- BEGIN LIBC
BACKTRACE -------At the moment the project uses classic caches. Private L1 and
shared L2 caches. I didn't test it with L3 caches as the simulation crashes
sometimes.Is it possible that the error occurs because of the classic caches
and cache coherence?Might the error vanish when using Ruby? An L3 cache should
also be implemented. Is it difficult to do that in Ruby?
Thank you very much for your help.
Best regardsSebastian
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
