[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bac9e91-36a0-c1d6-a887-4d60567ac75a@linux.intel.com>
Date: Mon, 12 Oct 2020 09:44:55 +0100
From: Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>,
Joerg Roedel <joro@...tes.org>, Tom Murphy <murphyt7@....ie>,
David Woodhouse <dwmw2@...radead.org>,
Christoph Hellwig <hch@...radead.org>
Cc: Ashok Raj <ashok.raj@...el.com>, Intel-gfx@...ts.freedesktop.org,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/7] Convert the intel iommu driver to the dma-iommu
api
On 29/09/2020 01:11, Lu Baolu wrote:
> Hi Tvrtko,
>
> On 9/28/20 5:44 PM, Tvrtko Ursulin wrote:
>>
>> On 27/09/2020 07:34, Lu Baolu wrote:
>>> Hi,
>>>
>>> The previous post of this series could be found here.
>>>
>>> https://lore.kernel.org/linux-iommu/20200912032200.11489-1-baolu.lu@linux.intel.com/
>>>
>>>
>>> This version introduce a new patch [4/7] to fix an issue reported here.
>>>
>>> https://lore.kernel.org/linux-iommu/51a1baec-48d1-c0ac-181b-1fba92aa428d@linux.intel.com/
>>>
>>>
>>> There aren't any other changes.
>>>
>>> Please help to test and review.
>>>
>>> Best regards,
>>> baolu
>>>
>>> Lu Baolu (3):
>>> iommu: Add quirk for Intel graphic devices in map_sg
>>
>> Since I do have patches to fix i915 to handle this, do we want to
>> co-ordinate the two and avoid having to add this quirk and then later
>> remove it? Or you want to go the staged approach?
>
> I have no preference. It depends on which patch goes first. Let the
> maintainers help here.
FYI we have merged the required i915 patches to out tree last week or
so. I *think* this means they will go into 5.11. So the i915 specific
workaround patch will not be needed in Intel IOMMU.
Regards,
Tvrtko
Powered by blists - more mailing lists