| commit | 3e090e3489dbae7af65465d357a4772f012f4d90 | |
| author | Peter Xu <peterx@redhat.com> | |
| Thu, 23 Feb 2023 06:59:24 +0000 (23 14:59 +0800) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Fri, 3 Mar 2023 00:13:52 +0000 (2 19:13 -0500) | ||
| tree | 3406a7a877ae22d8d47895ae3d968a8934b845e8 | treesnapshot (tar.gz zip) |
| parent | 98332f643ebf92523ad9128c0437d9fe964bfd09 | commitdiff |
intel-iommu: send UNMAP notifications for domain or global inv desc
We don't send UNMAP notification upon domain or global invalidation
which will lead the notifier can't work correctly. One example is to
use vhost remote IOTLB without enabling device IOTLB.
Fixing this by sending UNMAP notification.
Signed-off-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Message-Id: <20230223065924.42503-6-jasowang@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>
We don't send UNMAP notification upon domain or global invalidation
which will lead the notifier can't work correctly. One example is to
use vhost remote IOTLB without enabling device IOTLB.
Fixing this by sending UNMAP notification.
Signed-off-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Message-Id: <20230223065924.42503-6-jasowang@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>
| hw/i386/intel_iommu.c | diffblobblamehistory |