Re: [PATCH v13 03/15] iommu/dma: Allow MSI-only cookies

On 10/10/16 15:47, Auger Eric wrote: > Hi Robin, > > On 10/10/2016 16:26, Robin Murphy wrote: >> Hi Alex, Eric, >> >> On 06/10/16 21:17, Alex Williamson wrote: >>> On Thu, 6 Oct 2016 08:45:19 + >>> Eric Auger wrote: >>> From: Robin Murphy

Re: [PATCH v13 15/15] vfio/type1: Return the MSI geometry through VFIO_IOMMU_GET_INFO capability chains

Hi Alex, On 07/10/2016 22:38, Alex Williamson wrote: > On Fri, 7 Oct 2016 19:10:27 +0200 > Auger Eric wrote: > >> Hi Alex, >> >> On 06/10/2016 22:42, Alex Williamson wrote: >>> On Thu, 6 Oct 2016 14:20:40 -0600 >>> Alex Williamson wrote: >>>

Re: [PATCH v13 03/15] iommu/dma: Allow MSI-only cookies

Hi Robin, On 10/10/2016 16:26, Robin Murphy wrote: > Hi Alex, Eric, > > On 06/10/16 21:17, Alex Williamson wrote: >> On Thu, 6 Oct 2016 08:45:19 + >> Eric Auger wrote: >> >>> From: Robin Murphy >>> >>> IOMMU domain users such as VFIO face a

Re: [PATCH v13 03/15] iommu/dma: Allow MSI-only cookies

Hi Alex, Eric, On 06/10/16 21:17, Alex Williamson wrote: > On Thu, 6 Oct 2016 08:45:19 + > Eric Auger wrote: > >> From: Robin Murphy >> >> IOMMU domain users such as VFIO face a similar problem to DMA API ops >> with regard to mapping MSI

Re: [PATCH v4 2/2] iommu/exynos: Add proper runtime pm support

Hi Luis On 2016-10-06 19:37, Luis R. Rodriguez wrote: On Thu, Sep 29, 2016 at 10:12:31AM +0200, Marek Szyprowski wrote: This patch uses recently introduced device links to track the runtime pm state of the master's device. This way each SYSMMU controller is runtime activated when its master's

Re: [PATCH] iommu/vt-d: Fix the size calculation of pasid table

Ping David for confirmation On 2016/09/19 at 20:18, Joerg Roedel wrote: > [Cc'ing David] > > On Mon, Sep 12, 2016 at 10:49:11AM +0800, Xunlei Pang wrote: >> According to the vt-d spec, the size of pasid (state) entry is 8B >> which equals 3 in power of 2, the number of pasid (state) entries >> is

Re: [PATCH V3 0/8] IOMMU probe deferral support

Hi Sricharan, On 2016-10-04 19:03, Sricharan R wrote: Initial post from Laurent Pinchart[1]. This is series calls the dma ops configuration for the devices at a generic place so that it works for all busses. The dma_configure_ops for a device is now called during the device_attach callback