Skip to content

Commit

Permalink
docs/devel/reset: Document reset expectations for DMA and IOMMU
Browse files Browse the repository at this point in the history
To avoid any translation faults, the IOMMUs are expected to be
reset after the devices they protect. Document that we expect
DMA requests to be stopped during the 'enter' or 'hold' phase
while IOMMUs should be reset during the 'exit' phase.

Signed-off-by: Eric Auger <[email protected]>
Reviewed-by: Zhenzhong Duan <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
  • Loading branch information
eauger authored and mstsirkin committed Feb 21, 2025
1 parent d410e70 commit dd6d545
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/devel/reset.rst
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,11 @@ The *exit* phase is executed only when the last reset operation ends. Therefore
the object does not need to care how many of reset controllers it has and how
many of them have started a reset.

DMA capable devices are expected to cancel all outstanding DMA operations
during either 'enter' or 'hold' phases. IOMMUs are expected to reset during
the 'exit' phase and this sequencing makes sure no outstanding DMA request
will fault.


Handling reset in a resettable object
-------------------------------------
Expand Down

0 comments on commit dd6d545

Please sign in to comment.