qemu-e2k/include/exec
Peter Xu 8a7c606016 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>
2023-01-27 11:47:02 -05:00
..
user
address-spaces.h
confidential-guest-support.h
cpu_ldst.h
cpu-all.h
cpu-common.h
cpu-defs.h
cputlb.h
exec-all.h
gdbstub.h
gen-icount.h
helper-gen.h
helper-head.h
helper-proto.h
helper-tcg.h
hwaddr.h
ioport.h
log.h
memattrs.h
memop.h
memopidx.h
memory_ldst_cached.h.inc
memory_ldst_phys.h.inc
memory_ldst.h.inc
memory-internal.h
memory.h intel-iommu: Document iova_tree 2023-01-27 11:47:02 -05:00
page-vary.h
plugin-gen.h
poison.h
ram_addr.h
ramblock.h
ramlist.h
target_page.h
translate-all.h
translator.h