Hi,
I’m trying to debug a coherence bug caused by my customized garnet network (in short, the network generates its own invalidations to send to caches).
I’m reviewing the simulation log and seeing the invalidations generated within the network reach the network interface and eventually the L1/L2 cache controllers. Is there a way to log the coherence state transitions of the cache lines using a specific debug flag? I’m currently running with "RubyNetwork,RubyCache,RubySlicc,RubyGenerated” however my logs don’t show transition information.
Ideally the debug info printed would contain something like “cacheX lineY transitioned SHARED->INV”. I thought this would be included in the “RubySlicc” flag from the compiled SLICC code, but I’m not seeing anything.
Thanks in advance for any replies,
Vlad
Maybe try the ProtocolTrace
debug flag
On Thu, Apr 11, 2024 at 11:48 PM Vladimir Milicevic via gem5-users <
gem5-users@gem5.org> wrote:
Hi,
I’m trying to debug a coherence bug caused by my customized garnet network
(in short, the network generates its own invalidations to send to caches).
I’m reviewing the simulation log and seeing the invalidations generated
within the network reach the network interface and eventually the L1/L2
cache controllers. Is there a way to log the coherence state transitions of
the cache lines using a specific debug flag? I’m currently running with
"RubyNetwork,RubyCache,RubySlicc,RubyGenerated” however my logs don’t show
transition information.
Ideally the debug info printed would contain something like “cacheX lineY
transitioned SHARED->INV”. I thought this would be included in the
“RubySlicc” flag from the compiled SLICC code, but I’m not seeing anything.
Thanks in advance for any replies,
Vlad
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.org
That’s it. Thank you, Z.
On Apr 12, 2024, at 9:28 AM, Z HW via gem5-users gem5-users@gem5.org wrote:
[External Email]
Maybe try the ProtocolTrace
debug flag
On Thu, Apr 11, 2024 at 11:48 PM Vladimir Milicevic via gem5-users <gem5-users@gem5.orgmailto:gem5-users@gem5.org> wrote:
Hi,
I’m trying to debug a coherence bug caused by my customized garnet network (in short, the network generates its own invalidations to send to caches).
I’m reviewing the simulation log and seeing the invalidations generated within the network reach the network interface and eventually the L1/L2 cache controllers. Is there a way to log the coherence state transitions of the cache lines using a specific debug flag? I’m currently running with "RubyNetwork,RubyCache,RubySlicc,RubyGenerated” however my logs don’t show transition information.
Ideally the debug info printed would contain something like “cacheX lineY transitioned SHARED->INV”. I thought this would be included in the “RubySlicc” flag from the compiled SLICC code, but I’m not seeing anything.
Thanks in advance for any replies,
Vlad
gem5-users mailing list -- gem5-users@gem5.orgmailto:gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.orgmailto:gem5-users-leave@gem5.org
gem5-users mailing list -- gem5-users@gem5.orgmailto:gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.orgmailto:gem5-users-leave@gem5.org