Clarifications to PTE specification #469
Conversation
This clause order makes it more obvious from visual scanning that the difference is "and the capability read from memory has tag set". I also added "its" for grammar make good.
This makes it flow a bit better I think because the actual behaviour of CRG is separated from the atomicity & memory ordering requirements that I want to put off reading.
Explicitly say that they are still reserved in non-leaf nodes. This matches the behaviour for Svpmbt for example (and I copied some of the text from there).
Clarify that the PTE check for a tag when storing capabilities happens after they are potentially removed by permission checks.
Timmmm
force-pushed
the
user/timh/pte_tweaks
branch
from
0116f7f to
092803f
Compare
There was a problem hiding this comment.
We haven't previously specified when happens on non-leaf PTEs, and there's no reason to allocate these bits there so it's better if we define them to be reserved, so I think this is sensible.
The other edits are all no-change, just improving the formatting and explicitly pointing at that the tag clear on SC is before the PTE check.
@Timmmm has pointed out that it is just a clarification as the text only talks about leaf PTEs |
Some minor clarification & formatting improvements in the PTE spec. I can break these into separate PRs if you like. --------- Co-authored-by: Tariq Kurd <[email protected]>
Some minor clarification & formatting improvements in the PTE spec. I can break these into separate PRs if you like.