Skip to content

Commit

Permalink
Fix anchor declaration in table 2
Browse files Browse the repository at this point in the history
Signed-off-by: tyshyu <[email protected]>
  • Loading branch information
tyshyu authored Jan 6, 2025
1 parent ad6071e commit 1dbb9ff
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
2 changes: 1 addition & 1 deletion chapter2.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,7 @@ The following table shows (1) the error types, and (2) related control bits abou
* Receives an instruction fetch transaction when *HWCFG0.no_x* is 1
| Global
|0x06 2+| Unknown RRID | Global
|0x07 2+| Error due to a stalled transaction. Please refer <<#SECTION_4_2_1, Faulting stalled transactions>>.
|0x07 2+| Error due to a stalled transaction. Please refer <<#FAULTING_STALLED_TRANSACTIONS, Faulting stalled transactions>>.
| Global
|0x08 ~ 0x0D 2+| N/A, reserved for future | N/A
|0x0E ~ 0x0F 2+| User-defined error | Implementation-dependent
Expand Down
1 change: 1 addition & 0 deletions chapter4.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,7 @@ NOTE: When writing *MDSTALL*, the specification only defines the transactions wi
=== Cherry Pick
If *MDSTALL* doesn't stall all the desired transactions, there is an optional method to pick the transaction with specific RRIDs. The *RRIDSCP* register comprises two fields: a 2-bit *RRIDSCP.op* and a field for *RRIDSCP.rrid*. By setting *RRIDSCP.op*=1, the rrid_stall[_i_] is activated for __i__=*RRIDSCP.rrid*. Conversely, by setting *RRIDSCP.op*=2, the rrid_stall[_i_] is deactivated for _i_=*RRIDSCP.rrid*. This register is used to fine-tune the result of writing *MDSTALL*. The value of *RRIDSCP.op*=0 is to query the rrid_stall indirectly, and the value of 3 is reserved.

[#FAULTING_STALLED_TRANSACTIONS]
=== Faulting stalled transactions
Faulting stalled transactions can be allowed. To allow faulting over stalling when the IOPMP has no capacity to handle more stalls, one should set *ERR_CFG.stall_violation_en* to 1 before Step 1. If any transaction is faulted due to the stalled transactions, the error information shall be logged in *ERR_REQINFO*, where *ERR_REQINFO.etype* = 0x07 (error due to stalled transactions). The procedure for faulting checking transactions is identical to Steps 1-3 mentioned above, except that, besides stalling and delaying the transactions, transactions can be faulted and cannot be resumed if the IOPMP can't handle more stalled transactions.

Expand Down

0 comments on commit 1dbb9ff

Please sign in to comment.