search for: iommu_resv_mem_t_direct

> 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

> 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

...ing in stage2, e.g. from GPA of virtual doorbell to HPA of physical doorbell. But it doesn't like a good design - VFIO doesn't assign interrupt controller to user space then why should VFIO allow user mapping to doorbell... if 1) is agreed, looks the missing part in spec is just VIRTIO_ IOMMU_RESV_MEM_T_DIRECT, though the whole story is lengthy and fully enabling nested require many other works. :-) Thanks Kevin