search for: viommu1

...nterfacing with an IOMMU (or MSI controller), it > doesn't mean anything outside this context. Here the host allocates 13 > bits to platform device IDs, which is legal. > Please add such explanation to your next version. In earlier text "16-bits request ID" is mentioned for vIOMMU1, which gave me the illusion that same 16bit applies to vIOMMU2 too. Thanks Kevin

...nterfacing with an IOMMU (or MSI controller), it > doesn't mean anything outside this context. Here the host allocates 13 > bits to platform device IDs, which is legal. > Please add such explanation to your next version. In earlier text "16-bits request ID" is mentioned for vIOMMU1, which gave me the illusion that same 16bit applies to vIOMMU2 too. Thanks Kevin

> From: Jean-Philippe Brucker > Sent: Saturday, April 8, 2017 3:18 AM > > Unlike other virtio devices, the virtio-iommu doesn't work independently, > it is linked to other virtual or assigned devices. So before jumping into > device operations, we need to define a way for the guest to discover the > virtual IOMMU and the devices it translates. > > The host must

> From: Jean-Philippe Brucker > Sent: Saturday, April 8, 2017 3:18 AM > > Unlike other virtio devices, the virtio-iommu doesn't work independently, > it is linked to other virtual or assigned devices. So before jumping into > device operations, we need to define a way for the guest to discover the > virtual IOMMU and the devices it translates. > > The host must