>OK, so that's really just another variant of the existing problem we have with
>certain PCI root complexes with restrictive inbound windows.
>The appropriate way to handle that is to reserve the unusable areas of the
>IOVA space up-front.
> Since the support for the ACPI equivalent of "dma-range
to:robin.mur...@arm.com]
> Sent: Friday, September 1, 2017 2:43 AM
> To: Joerg Roedel ; Krishna Reddy
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] iommu/dma: limit the IOVA allocated to dma-ranges region
>
> On 01/09/17 10:2
mber 1, 2017 2:43 AM
To: Joerg Roedel ; Krishna Reddy
Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/dma: limit the IOVA allocated to dma-ranges region
On 01/09/17 10:26, Joerg Roedel wrote:
> Adding Robin for review.
>
> On Thu, Aug 31, 2017
On 01/09/17 10:26, Joerg Roedel wrote:
> Adding Robin for review.
>
> On Thu, Aug 31, 2017 at 03:08:21PM -0700, Krishna Reddy wrote:
>> Limit the IOVA allocated to dma-ranges specified for the device.
>> This is necessary to ensure that IOVA allocated is addressable
>> by device.
Why? IOVA alloca
Adding Robin for review.
On Thu, Aug 31, 2017 at 03:08:21PM -0700, Krishna Reddy wrote:
> Limit the IOVA allocated to dma-ranges specified for the device.
> This is necessary to ensure that IOVA allocated is addressable
> by device.
>
> Signed-off-by: Krishna Reddy
> ---
> drivers/iommu/dma-iom
Limit the IOVA allocated to dma-ranges specified for the device.
This is necessary to ensure that IOVA allocated is addressable
by device.
Signed-off-by: Krishna Reddy
---
drivers/iommu/dma-iommu.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu
6 matches
Mail list logo