Skip to content

Commit

Permalink
Clarify that IOTINVAL behavior for invalid addresses
Browse files Browse the repository at this point in the history
  • Loading branch information
ved-rivos committed Feb 24, 2024
1 parent 9ab27af commit 00bf25c
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion iommu_in_memory_queues.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,10 @@ operand is valid. Setting `PSCV` to 1 is allowed only for `IOTINVAL.VMA`. The
the translations associated with the host (i.e. those where the second-stage
is Bare) are operated on. When `GV` is 0, the `GSCID` operand is ignored.
When `AV` is 0, the `ADDR` operand is ignored. When `PSCV` operand is 0, the
`PSCID` operand is ignored.
`PSCID` operand is ignored. When the `AV` operand is set to 1, if the `ADDR`
operand specifies an invalid address, the implementation may either complete the
command with no effect or may complete the command using an alternate, yet
`UNSPECIFIED`, legal value for the `ADDR` operand.

`IOTINVAL.VMA` ensures that previous stores made to the first-stage page
tables by the harts are observed by the IOMMU before all subsequent implicit
Expand Down

0 comments on commit 00bf25c

Please sign in to comment.