* [RPC]: iommu/dma: custom iommu_setup_dma_ops for secure iommu
@ 2023-03-07 10:52 Hsia-Jun Li
0 siblings, 0 replies; only message in thread
From: Hsia-Jun Li @ 2023-03-07 10:52 UTC (permalink / raw)
To: iommu; +Cc: linux-kernel, robin.murphy, joro, will
Hello All
If I want to implement a secure IOMMU. Is there any way other than hook
the iommu_setup_dma_ops() I still want to use the of(device tree) helper?
The secure IOMMU is a little different from the existing secure
attribute page table. The physical address and iova address not
available for the Linux environment(REE), even they are available, they
can't be configured to the secure device directly. So we don't need the
Linux kernel to allocate the iova address for us, means I need to
replace the current iommu_dma_map_sg() implementation.
Even sometimes it didn't do the iommu work, just allocate a secure
reference page id for a continuous memory. I think the iommu framework
is the most proper framework to implement this feature, it just fit the
steps of importing a buffer for the secure world.
Please give me some advice on this idea.
--
Hsia-Jun(Randy) Li
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-03-07 10:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-07 10:52 [RPC]: iommu/dma: custom iommu_setup_dma_ops for secure iommu Hsia-Jun Li
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.