You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to new messages, TL-C specifies implied permission transfers for these existing messages from TL-UL and TL-UH.
Get implicitly Cap the permissions as None (Invalid).
{PutFullData, PutPartialData, ArithmeticData, LogicalData} implicitly Cap the permissions as not Read+Write [Trunk] or [Tip], i.e. as None [Invalid] or Read [Branch].
From above section of the spec, we understand if a data block is already acquired and the TL-UH command is tried from one Core (i.e. M1) then it affects the permission of the Cache attached to M1.
Queries:
Suppose we have Acquired a block, then send Get for that block. As per my understanding if a data block is Acquired, with at least with Read permission and assuming this access is not released then that Master/Core should not get Read miss and so should not send Get command further. So in which case this scenario might arise? Please confirm whether my understanding correct?
With sending Transfer Access command from Master to Slave, does the permission automatically updated or any additional Probe command needed? Because as specified in spec the permission is capped.
Does it impact other Cores as well? If yes how would slave conveys? Does it send Probe command?
If we send PutFullData after a Acquire message with Read+Write permission, then the permission can be reduced to None or Read only. How we decide which permission to achieve? Who decides it whether Master or Slave?
Regards,
Asutosh
The text was updated successfully, but these errors were encountered:
Ahh it isn't the same question.
The question on the google group is related to aquire BtoT / probe toN interaction.
This github issue seems more related to the interraction of block ownership / (get+put) emited from a given master agent.
Ahh it isn't the same question. The question on the google group is related to aquire BtoT / probe toN interaction. This github issue seems more related to the interraction of block ownership / (get+put) emited from a given master agent.
Apologies, I made a mistake and deleted my earlier post here to avoid confusion, but may have actually caused it! ☹️
Hi,
We have few doubts on Tilleink spec.
9.4. TL-UL and TL-UH Messages on Channel A and D
In addition to new messages, TL-C specifies implied permission transfers for these existing messages from TL-UL and TL-UH.
Get implicitly Cap the permissions as None (Invalid).
{PutFullData, PutPartialData, ArithmeticData, LogicalData} implicitly Cap the permissions as not Read+Write [Trunk] or [Tip], i.e. as None [Invalid] or Read [Branch].
From above section of the spec, we understand if a data block is already acquired and the TL-UH command is tried from one Core (i.e. M1) then it affects the permission of the Cache attached to M1.
Queries:
Regards,
Asutosh
The text was updated successfully, but these errors were encountered: