Hi Ziyao, Even though protocols are often implemented that way, SLICC does not require that each request type corresponds to an event type. For instance, the event can be a function of both an incoming message type and of the internal state of the controller. The only true way to understand what triggers each event is to look at the source code of the state machine (e.g., MESI_Three_Level-L1cache.sm for le L1). Look for all trigger statements and check under which conditions they are reached.
Regards, Gabriel
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
