[lkml]   [2019]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/9] iommu/dma-iommu: Add iommu_dma_copy_reserved_iova, iommu_dma_apply_resv_region to the dma-iommu api
On 16/04/2019 14:22, Tom Murphy wrote:
> I hoped this could be an exception, it's easier to grok without the
> line break and isn't crazy long. Because you mentioned it I'll fix it.

Frankly this patch is hard to justify anyway - iommu-dma already has its
own reserved region handling, and there should be no need for external
callers to be poking into the innards provided the IOMMU driver reports
the correct reserved regions in the first place.

If the iommu-dma abstraction is not quite sufficient to actually convert
amd-iommu to use it properly, then we should improve the abstraction,
rather than just punching holes in it to merely poke renamed parts of
the existing amd-iommu logic into.


> On Mon, Apr 15, 2019 at 7:31 AM Christoph Hellwig <> wrote:
>> On Thu, Apr 11, 2019 at 07:47:32PM +0100, Tom Murphy via iommu wrote:
>>> +
>>> + WARN_ON_ONCE(iommu_dma_reserve_iova(domain, region->start, end) == NULL);
>> Overly long line..

 \ /
  Last update: 2019-04-16 15:38    [W:0.046 / U:1.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site