Hello,
Without digging deeper into things, I *believe* `Writeback_Ack_Data` has
the data with the acknowledgement, but `Writeback_Ack` just has the ack.
That's why you have to send the data from the TBE if you receive a
Writeback_Ack_Data.
Cheers,
Jason
On Fri, Sep 25, 2020 at 6:26 AM 1154063264--- via gem5-dev <
gem5-dev@gem5.org> wrote:
> MOESI_CMP_directory-L1cache.sm , what is the difference between the events
> Writeback_Ack_Data and Writeback_Ack?
>
> Writeback_Ack, desc="Writeback O.K. from directory";
> Writeback_Ack_Data, desc="Writeback O.K. from directory";
>
> When the Writeback_Ack is triggered, there is no qq_sendWBDataFromTBEToL2,
> why the state is still converted to I ?
> transition({SI, OI, MI}, Writeback_Ack, I) {
> g_sendUnblock;
> s_deallocateTBE;
> l_popForwardQueue;
> }
> transition({SI, OI, MI}, Writeback_Ack_Data, I) {
> qq_sendWBDataFromTBEToL2; // always send data
> s_deallocateTBE;
> l_popForwardQueue;
> }
> _______________________________________________
> gem5-dev mailing list -- gem5-dev@gem5.org
> To unsubscribe send an email to gem5-dev-le...@gem5.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
_______________________________________________
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
