diff options
| author | Leon Romanovsky <leonro@nvidia.com> | 2026-01-31 07:34:18 +0200 |
|---|---|---|
| committer | Christian König <christian.koenig@amd.com> | 2026-02-23 19:51:41 +0100 |
| commit | 8c5f9645c3893f0db679d9affe4fe4e665b990dd (patch) | |
| tree | 559864b5593de3697db87bd902482827b9255544 /tools/perf/scripts/python | |
| parent | 6ffe939bf94fbbeaaa4050a0e9c22820e959b15f (diff) | |
iommufd: Add dma_buf_pin()
IOMMUFD relies on a private protocol with VFIO, and this always operated
in pinned mode.
Now that VFIO can support pinned importers update IOMMUFD to invoke the
normal dma-buf flow to request pin.
This isn't enough to allow IOMMUFD to work with other exporters, it still
needs a way to get the physical address list which is another series.
IOMMUFD supports the defined revoke semantics. It immediately stops and
fences access to the memory inside it's invalidate_mappings() callback,
and it currently doesn't use scatterlists so doesn't call map/unmap at
all.
It is expected that a future revision can synchronously call unmap from
the move_notify callback as well.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Acked-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Christian König <christian.koenig@amd.com>
Link: https://lore.kernel.org/r/20260131-dmabuf-revoke-v7-8-463d956bd527@nvidia.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
