Re: [PATCH v5 7/7] iommu/exynos: Use device dependency links to control runtime pm

Hi Luis, On 2016-11-07 22:47, Luis R. Rodriguez wrote: On Thu, Oct 20, 2016 at 09:22:53AM +0200, Marek Szyprowski wrote: This patch uses recently introduced device dependency links to track the runtime pm state of the master's device. This way each SYSMMU controller is set to runtime active

RE: [v15, 3/7] powerpc/fsl: move mpc85xx.h to include/linux/fsl

Hi Arnd, > -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Tuesday, November 08, 2016 5:20 AM > To: Y.B. Lu > Cc: linuxppc-...@lists.ozlabs.org; linux-...@vger.kernel.org; > ulf.hans...@linaro.org; Scott Wood; Mark Rutland; Greg Kroah-Hartman; X.B. > Xie; M.H.

Summary of LPC guest MSI discussion in Santa Fe (was: Re: [RFC 0/8] KVM PCIe/MSI passthrough on ARM/ARM64 (Alt II))

Hi all, I figured this was a reasonable post to piggy-back on for the LPC minutes relating to guest MSIs on arm64. On Thu, Nov 03, 2016 at 10:02:05PM -0600, Alex Williamson wrote: > We can always have QEMU reject hot-adding the device if the reserved > region overlaps existing guest RAM, but I

Re: [PATCH v5 7/7] iommu/exynos: Use device dependency links to control runtime pm

On Thu, Oct 20, 2016 at 09:22:53AM +0200, Marek Szyprowski wrote: > This patch uses recently introduced device dependency links to track the > runtime pm state of the master's device. This way each SYSMMU controller > is set to runtime active only when its master's device is active and can >

Re: [v15, 3/7] powerpc/fsl: move mpc85xx.h to include/linux/fsl

On Monday, October 31, 2016 9:35:33 AM CET Y.B. Lu wrote: > > > > I don't see any of the contents of this header referenced by the soc > > driver any more. I think you can just drop this patch. > > > > [Lu Yangbo-B47093] This header file was included by guts.c. > The guts driver used macro

Re: Re: Crash/hang in iommu_flush_dev_iotlb

Hi Brian, I suspect it might be a race condition that causes domain == NULL in iommu_flush_dev_iotlb(). Can you help me reproduce it? what workload and device you are using etc. Thanks, Jacob ___ iommu mailing list iommu@lists.linux-foundation.org

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

On Fri, Nov 04, 2016 at 08:46:06PM +0530, Sricharan wrote: > >>>Yikes, on second look, that definitely shouldn't be happening. > >>>Everything below is probably the resulting fallout. > >> > >>[ 40.206703] vfio-pci :08:00.0: Failed to setup iommu ops > >> > >>I think the above print which

Re: [PATCH 2/2] swiotlb: Add swiotlb=nobounce debug option

Hi Konrad, On Mon, Oct 31, 2016 at 6:52 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Oct 31, 2016 at 04:45:04PM +0100, Geert Uytterhoeven wrote: >> On architectures like arm64, swiotlb is tied intimately to the core >> architecture DMA support. In addition, ZONE_DMA cannot

[PATCH v2] iommu/arm-smmu: Fix out-of-bounds dereference

When we iterate a master's config entries, what we generally care about is the entry's stream map index, rather than the entry index itself, so it's nice to have the iterator automatically assign the former from the latter. Unfortunately, booting with KASAN reveals the oversight that using a

Re: [PATCH] iommu/arm-smmu: Fix out-of-bounds dereference

On Mon, Nov 07, 2016 at 03:39:02PM +, Robin Murphy wrote: > When we iterate a master's config entries, what we generally care > about is the entry's stream map index, rather than the entry index > itself, so it's nice to have the iterator automatically assign the > former from the latter.

Re: [PATCH 2/2] swiotlb: Add swiotlb=nobounce debug option

Hi Geert, On 07/11/16 15:41, Geert Uytterhoeven wrote: > Hi Robin, > > On Tue, Nov 1, 2016 at 12:46 PM, Robin Murphy wrote: > To aid debugging and catch devices not supporting DMA to memory outside > the 32-bit address space, add a kernel command line option >

Re: [PATCH] iommu/arm-smmu: Fix out-of-bounds dereference

On Mon, Nov 07, 2016 at 03:39:02PM +, Robin Murphy wrote: > When we iterate a master's config entries, what we generally care > about is the entry's stream map index, rather than the entry index > itself, so it's nice to have the iterator automatically assign the > former from the latter.

Re: [PATCH 2/2] swiotlb: Add swiotlb=nobounce debug option

Hi Robin, On Tue, Nov 1, 2016 at 12:46 PM, Robin Murphy wrote: To aid debugging and catch devices not supporting DMA to memory outside the 32-bit address space, add a kernel command line option "swiotlb=nobounce", which disables the use of bounce buffers.

[PATCH] iommu/arm-smmu: Fix out-of-bounds dereference

When we iterate a master's config entries, what we generally care about is the entry's stream map index, rather than the entry index itself, so it's nice to have the iterator automatically assign the former from the latter. Unfortunately, booting with KASAN reveals the oversight that using a

[PATCH] iommu/dma-iommu: properly respect configured address space size

When one called iommu_dma_init_domain() with size smaller than device's DMA mask, the alloc_iova() will not respect it and always assume that all IOVA addresses will be allocated from the the (base ... dev->dma_mask) range. This patch fixes this issue by taking the configured address space size

Re: [PATCH v6 09/16] drivers: acpi: iort: add support for ARM SMMU platform devices creation

On Tue, Nov 01, 2016 at 04:30:22PM -0600, Graeme Gregory wrote: > On Fri, Oct 28, 2016 at 04:50:07PM +0100, Lorenzo Pieralisi wrote: > > On Tue, Oct 18, 2016 at 05:04:07PM +0100, Lorenzo Pieralisi wrote: > > > In ARM ACPI systems, IOMMU components are specified through static > > > IORT table

Re: [PATCH v6 04/16] drivers: iommu: make of_iommu_set/get_ops() DT agnostic

On Tue, Nov 01, 2016 at 04:36:10PM +, Robin Murphy wrote: > Bikeshed alert... > > On 18/10/16 17:04, Lorenzo Pieralisi wrote: > > The of_iommu_{set/get}_ops() API is used to associate a device > > tree node with a specific set of IOMMU operations. The same > > kernel interface is required on