search for: iommu_dma_get

Displaying 3 results from an estimated 3 matches for "iommu_dma_get".

2018 Mar 21
4
[PATCH 1/4] iommu: Add virtio-iommu driver
> From: Jean-Philippe Brucker [mailto:jean-philippe.brucker at arm.com] > Sent: Wednesday, February 14, 2018 10:54 PM > > The virtio IOMMU is a para-virtualized device, allowing to send IOMMU > requests such as map/unmap over virtio-mmio transport without > emulating > page tables. This implementation handles ATTACH, DETACH, MAP and > UNMAP > requests. > > The
2018 Mar 21
4
[PATCH 1/4] iommu: Add virtio-iommu driver
> From: Jean-Philippe Brucker [mailto:jean-philippe.brucker at arm.com] > Sent: Wednesday, February 14, 2018 10:54 PM > > The virtio IOMMU is a para-virtualized device, allowing to send IOMMU > requests such as map/unmap over virtio-mmio transport without > emulating > page tables. This implementation handles ATTACH, DETACH, MAP and > UNMAP > requests. > > The
2018 Mar 23
0
[PATCH 1/4] iommu: Add virtio-iommu driver
...figuration anyway. > > > > Robin. > > Curious since anyway we are defining a new iommu architecture > is it possible to avoid those ARM-specific burden completely? > OK, after some study around those tricks below is my learning: - MSI_IOVA window is used only on request (iommu_dma_get _msi_page), not meant to take effect on all architectures once initialized. e.g. ARM GIC does it but not x86. So it is reasonable for virtio-iommu driver to implement such capability; - I thought whether hardware MSI doorbell can be always reported on virtio-iommu since it's newly defined. L...