search for: ioasids

...of address spaces (described by > ioasid_bits) might be a restriction of the pIOMMU. For page-table sharing > you still need to define which devices will share a page directory using > ATTACH requests, though that interface is not set in stone. got you. yes VM is supposed to consume less IOASIDs than physically available. It doesn?t hurt to have one IOASID space for both IOVA map/unmap usages (one IOASID per device) and SVM usages (multiple IOASIDs per device). The former is digested by software and the latter will be bound to hardware. Thanks Kevin

...of address spaces (described by > ioasid_bits) might be a restriction of the pIOMMU. For page-table sharing > you still need to define which devices will share a page directory using > ATTACH requests, though that interface is not set in stone. got you. yes VM is supposed to consume less IOASIDs than physically available. It doesn?t hurt to have one IOASID space for both IOVA map/unmap usages (one IOASID per device) and SVM usages (multiple IOASIDs per device). The former is digested by software and the latter will be bound to hardware. Thanks Kevin

> From: Jean-Philippe Brucker > Sent: Saturday, April 8, 2017 3:18 AM > [...] > II. Feature bits > ================ > > VIRTIO_IOMMU_F_INPUT_RANGE (0) > Available range of virtual addresses is described in input_range Usually only the maximum supported address bits are important. Curious do you see such situation where low end of the address space is not usable

> From: Jean-Philippe Brucker > Sent: Saturday, April 8, 2017 3:18 AM > [...] > II. Feature bits > ================ > > VIRTIO_IOMMU_F_INPUT_RANGE (0) > Available range of virtual addresses is described in input_range Usually only the maximum supported address bits are important. Curious do you see such situation where low end of the address space is not usable

This is the initial proposal for a paravirtualized IOMMU device using virtio transport. It contains a description of the device, a Linux driver, and a toy implementation in kvmtool. With this prototype, you can translate DMA to guest memory from emulated (virtio), or passed-through (VFIO) devices. In its simplest form, implemented here, the device handles map/unmap requests from the guest. Future

This is the initial proposal for a paravirtualized IOMMU device using virtio transport. It contains a description of the device, a Linux driver, and a toy implementation in kvmtool. With this prototype, you can translate DMA to guest memory from emulated (virtio), or passed-through (VFIO) devices. In its simplest form, implemented here, the device handles map/unmap requests from the guest. Future

On 18/04/17 11:26, Tian, Kevin wrote: >> From: Jean-Philippe Brucker >> Sent: Saturday, April 8, 2017 3:18 AM >> > [...] >> II. Feature bits >> ================ >> >> VIRTIO_IOMMU_F_INPUT_RANGE (0) >> Available range of virtual addresses is described in input_range > > Usually only the maximum supported address bits are important.