Hi Sampad, I believe this relates to the fact that the coherence protocol is not actually sending out the data, but instead gem5 uses the backing store to functionally read/write data. Essentially, in a real system, yes we would need to send the data, which is why the message size accounts for this. But in a simulator we don't pass the data along to simplify things (i.e., we don't send the data, but we do account for it).
However, Alex and Brad (CC'd) know a lot more about the state of the backing store than I do, so they should comment to confirm. Matt On Tue, Aug 25, 2020 at 10:23 AM Sampad Mohapatra via gem5-users < gem5-users@gem5.org> wrote: > Hello, > > In GPU_VIPER-TCC.sm and GPU_TCP-TCP.sm, in action *at_atomicThrough* > present in both files, > the out message Type is *CoherenceRequestType:Atomic* and the message > size is *MessageSizeType:Data*, > but there is *no data* being sent. Is this correct behaviour ? > > Either data is not being sent or the message size should be some other > type. > Please advise. > > Thank you, > Sampad Mohapatra > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> > <#m_7456722988425397407_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > 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
_______________________________________________ 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
