• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 91 subscribers
  • Views 1014 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

In CHI spec, if the Requester initial state is UD or SD, what the final cache state of a ReadClean transaction should be?

Hobo

In CHI specification,

Table 4-33 shows that the Requester final cache state of a ReadClean transaction is UD/SD while its initial state is UD/SD/UDP.

But in Table 4-5, it seems that only UC/SC state is permitted for ReadClean request.

Why is that?

Parents
  • 0

    This an error/oversight in the CHI Specification for Table 4-5.

    Previously, it was not legal to issue ReadClean from anything other than a Invalid or UCE state, and so UC and SC were the only valid final states.  

    However, with MTE, if ReadClean has TagOp = Transfer then it is legal to issue ReadClean from other states and so SD and UD are valid final states.  The reason for this is that the RN might have valid data, but invalid tags.

Reply
  • 0

    This an error/oversight in the CHI Specification for Table 4-5.

    Previously, it was not legal to issue ReadClean from anything other than a Invalid or UCE state, and so UC and SC were the only valid final states.  

    However, with MTE, if ReadClean has TagOp = Transfer then it is legal to issue ReadClean from other states and so SD and UD are valid final states.  The reason for this is that the RN might have valid data, but invalid tags.

Children
No data