Re: [PATCH 2/2] iommu/vt-d: Work around broken RMRR firmware entries

2014-10-06 Thread Jiang Liu
On 2014/10/2 18:09, Joerg Roedel wrote: > From: Joerg Roedel > > The VT-d specification states that an RMRR entry in the DMAR > table needs to specify the full path to the device. This is > also how newer Linux kernels implement it. > > Unfortunatly older drivers just match for the target devic

Re: [RFC][PATCH 2/2] Add support of the IOMMU_DEVICE flag.

2014-10-06 Thread Mitchel Humpherys
On Mon, Oct 06 2014 at 03:28:16 AM, Varun Sethi wrote: > This flag is used for specifying access to device memory. SMMU would apply > device memory attributes for a DMA transaction. This is required for setting > access to GIC registers, for generating message interrupts. This would ensure > tha

Re: [PATCH v5 1/1] iommu-api: Add map_sg/unmap_sg functions

2014-10-06 Thread Olav Haugan
On 9/25/2014 10:01 AM, Joerg Roedel wrote: On Mon, Aug 11, 2014 at 03:45:50PM -0700, Olav Haugan wrote: +static inline int iommu_map_sg(struct iommu_domain *domain, unsigned long iova, + struct scatterlist *sg, unsigned int nents, + int p

Re: [RFC][PATCH 1/2] Introduce the IOMMU_DEVICE flag.

2014-10-06 Thread Olav Haugan
On 10/6/2014 4:04 AM, Will Deacon wrote: Hi Varun, [adding the Qualcomm guys, as I have an open question below] On Mon, Oct 06, 2014 at 11:28:15AM +0100, Varun Sethi wrote: This is used for indicating device memory type for a DMA transaction. IOMMU driver would set up attributes indicationg ac

Re: [RFC PATCH v3 7/7] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops

2014-10-06 Thread Thierry Reding
On Mon, Oct 06, 2014 at 01:50:40PM +0300, Laurent Pinchart wrote: > Hi Thierry and Will, > > On Monday 06 October 2014 11:52:50 Thierry Reding wrote: > > On Fri, Oct 03, 2014 at 04:08:50PM +0100, Will Deacon wrote: > > > On Wed, Oct 01, 2014 at 09:46:10AM +0100, Thierry Reding wrote: > > >> On Tue

Re: [PATCH 2/5] iommu/arm-smmu: add support for PCI master devices

2014-10-06 Thread Will Deacon
Hi Alex, On Wed, Jul 09, 2014 at 03:13:04PM +0100, Alex Williamson wrote: > On Wed, 2014-07-09 at 14:26 +0100, Will Deacon wrote: > > pci_find_dma_isolation_root doesn't exist in any of the trees I have. Alex, > > is this queued anywhere and do I actually need it? > > That function was in the v3

RE: [RFC][PATCH 1/2] Introduce the IOMMU_DEVICE flag.

2014-10-06 Thread Varun Sethi
Hi Will, > -Original Message- > From: Will Deacon [mailto:will.dea...@arm.com] > Sent: Monday, October 06, 2014 4:34 PM > To: Sethi Varun-B16395 > Cc: iommu@lists.linux-foundation.org; mitch...@codeaurora.org; > ohau...@codeaurora.org > Subject: Re: [RFC][PATCH 1/2] Introduce the IOMMU_DEV

RE: [RFC][PATCH 2/2] Add support of the IOMMU_DEVICE flag.

2014-10-06 Thread Varun Sethi
> -Original Message- > From: Will Deacon [mailto:will.dea...@arm.com] > Sent: Monday, October 06, 2014 4:47 PM > To: Sethi Varun-B16395 > Cc: iommu@lists.linux-foundation.org > Subject: Re: [RFC][PATCH 2/2] Add support of the IOMMU_DEVICE flag. > > On Mon, Oct 06, 2014 at 11:28:16AM +010

Re: [RFC][PATCH 2/2] Add support of the IOMMU_DEVICE flag.

2014-10-06 Thread Will Deacon
On Mon, Oct 06, 2014 at 11:28:16AM +0100, Varun Sethi wrote: > This flag is used for specifying access to device memory. SMMU would apply > device memory attributes for a DMA transaction. This is required for setting > access to GIC registers, for generating message interrupts. This would ensure >

Re: [RFC][PATCH 1/2] Introduce the IOMMU_DEVICE flag.

2014-10-06 Thread Will Deacon
Hi Varun, [adding the Qualcomm guys, as I have an open question below] On Mon, Oct 06, 2014 at 11:28:15AM +0100, Varun Sethi wrote: > This is used for indicating device memory type for a DMA transaction. IOMMU > driver would set up attributes indicationg access to device memory. > > Signed-off-b

Re: [RFC PATCH v3 7/7] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops

2014-10-06 Thread Laurent Pinchart
Hi Thierry and Will, On Monday 06 October 2014 11:52:50 Thierry Reding wrote: > On Fri, Oct 03, 2014 at 04:08:50PM +0100, Will Deacon wrote: > > On Wed, Oct 01, 2014 at 09:46:10AM +0100, Thierry Reding wrote: > >> On Tue, Sep 30, 2014 at 05:00:35PM +0100, Will Deacon wrote: > >>> On Thu, Sep 25, 2

[RFC][PATCH 1/2] Introduce the IOMMU_DEVICE flag.

2014-10-06 Thread Varun Sethi
This is used for indicating device memory type for a DMA transaction. IOMMU driver would set up attributes indicationg access to device memory. Signed-off-by: Varun Sethi --- include/linux/iommu.h |1 + 1 file changed, 1 insertion(+) diff --git a/include/linux/iommu.h b/include/linux/iommu.

[RFC][PATCH 2/2] Add support of the IOMMU_DEVICE flag.

2014-10-06 Thread Varun Sethi
This flag is used for specifying access to device memory. SMMU would apply device memory attributes for a DMA transaction. This is required for setting access to GIC registers, for generating message interrupts. This would ensure that transactions targetting device memory are not gathered or reor

Re: [PATCH v2] cma: make default CMA area size zero for x86

2014-10-06 Thread Marek Szyprowski
Hello, On 2014-10-05 15:54, Akinobu Mita wrote: This makes CMA memory area size zero for x86 in default configuration (doesn't change on the other architectures). If default CMA size is zero, DMA_CMA is disabled. It can be enabled by passing cma= to the kernel. This makes less impact on x86.

Re: [RFC PATCH v3 7/7] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops

2014-10-06 Thread Thierry Reding
On Fri, Oct 03, 2014 at 04:08:50PM +0100, Will Deacon wrote: > Hi Thierry, > > On Wed, Oct 01, 2014 at 09:46:10AM +0100, Thierry Reding wrote: > > On Tue, Sep 30, 2014 at 05:00:35PM +0100, Will Deacon wrote: > > > On Thu, Sep 25, 2014 at 07:40:23AM +0100, Thierry Reding wrote: > > [...] > > > > So