aboutsummaryrefslogtreecommitdiff
path: root/hw
diff options
context:
space:
mode:
authorPeter Xu <peterx@redhat.com>2023-01-09 14:37:27 -0500
committerMichael S. Tsirkin <mst@redhat.com>2023-01-27 11:47:02 -0500
commit8a7c606016d283a1716290c657f6f45bc7c4d817 (patch)
tree824a507afcc15711d5dab06cb9b1bd65218e13f2 /hw
parentbad9c5a5166fd5e3a892b7b0477cf2f4bd3a959a (diff)
downloadqemu-8a7c606016d283a1716290c657f6f45bc7c4d817.zip
qemu-8a7c606016d283a1716290c657f6f45bc7c4d817.tar.gz
qemu-8a7c606016d283a1716290c657f6f45bc7c4d817.tar.bz2
intel-iommu: Document iova_tree
It seems not super clear on when iova_tree is used, and why. Add a rich comment above iova_tree to track why we needed the iova_tree, and when we need it. Also comment for the map/unmap messages, on how they're used and implications (e.g. unmap can be larger than the mapped ranges). Suggested-by: Jason Wang <jasowang@redhat.com> Signed-off-by: Peter Xu <peterx@redhat.com> Message-Id: <20230109193727.1360190-1-peterx@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'hw')
0 files changed, 0 insertions, 0 deletions