diff options
| author | Eric Auger <eric.auger@redhat.com> | 2025-02-18 19:25:33 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2025-02-21 07:21:25 -0500 |
| commit | e39e3f8b8dea856f141e9945167d2b18021ef445 (patch) | |
| tree | 1dd8fbcc6067c4e9f404146d82c14af2ca9e54ad /rust/qemu-api/src/qom.rs | |
| parent | 2aaf48bcf27d8b3da5b30af6c1ced464d3df30f7 (diff) | |
| download | qemu-e39e3f8b8dea856f141e9945167d2b18021ef445.zip qemu-e39e3f8b8dea856f141e9945167d2b18021ef445.tar.gz qemu-e39e3f8b8dea856f141e9945167d2b18021ef445.tar.bz2 | |
hw/arm/smmuv3: Move reset to exit phase
Currently the iommu may be reset before the devices
it protects. For example this happens with virtio-scsi-pci.
when system_reset is issued from qmp monitor: spurious
"virtio: zero sized buffers are not allowed" warnings can
be observed. This happens because outstanding DMA requests
are still happening while the SMMU gets reset.
This can also happen with VFIO devices. In that case
spurious DMA translation faults can be observed on host.
Make sure the SMMU is reset in the 'exit' phase after
all DMA capable devices have been reset during the 'enter'
or 'hold' phase.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Message-Id: <20250218182737.76722-4-eric.auger@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'rust/qemu-api/src/qom.rs')
0 files changed, 0 insertions, 0 deletions