Displaying 4 results from an estimated 4 matches for "iommu_dma_map_msi_msg".
2018 Mar 21
2
[virtio-dev] [RFC] virtio-iommu version 0.6
...hat, no change
needed in the guest.
> Then what's the real point of differentiating MSI bypass from
> normal reserved range? Is there other example where guest
> may use such info to do special thing?
The presence of an MSI bypass regions allows the driver and the DMA layer
(in Linux iommu_dma_map_msi_msg) to know whether it needs to create a
mapping or if it's bypassed. When writing the entry into the MSI-X table,
if the address in the MSI vector already corresponds to an MSI bypass
region, then there is no need to create a mapping. Making the bypass MSI
region a normal RESV range hides that in...
2018 Mar 21
2
[virtio-dev] [RFC] virtio-iommu version 0.6
...hat, no change
needed in the guest.
> Then what's the real point of differentiating MSI bypass from
> normal reserved range? Is there other example where guest
> may use such info to do special thing?
The presence of an MSI bypass regions allows the driver and the DMA layer
(in Linux iommu_dma_map_msi_msg) to know whether it needs to create a
mapping or if it's bypassed. When writing the entry into the MSI-X table,
if the address in the MSI vector already corresponds to an MSI bypass
region, then there is no need to create a mapping. Making the bypass MSI
region a normal RESV range hides that in...
2018 Mar 22
0
[virtio-dev] [RFC] virtio-iommu version 0.6
...>
> > Then what's the real point of differentiating MSI bypass from
> > normal reserved range? Is there other example where guest
> > may use such info to do special thing?
>
> The presence of an MSI bypass regions allows the driver and the DMA layer
> (in Linux iommu_dma_map_msi_msg) to know whether it needs to create a
> mapping or if it's bypassed. When writing the entry into the MSI-X table,
> if the address in the MSI vector already corresponds to an MSI bypass
> region, then there is no need to create a mapping. Making the bypass MSI
> region a normal RESV...
2018 Feb 06
2
[RFC] virtio-iommu version 0.6
Please find version 0.6 of the virtio-iommu specification at the following
locations.
Document: http://jpbrucker.net/virtio-iommu/spec/virtio-iommu.pdf
http://jpbrucker.net/virtio-iommu/spec/virtio-iommu.html
Sources: git://linux-arm.org/virtio-iommu.git viommu/v0.6
I didn't receive any comment for v0.5 [1], so this update is fairly light:
* Changed range definition in map and