[PATCH] iommu/amd: flush IOTLB for specific domains only (v3)

Nath, Arindam Arindam.Nath at amd.com
Tue Sep 12 09:02:59 UTC 2017


Hi Daniel,

>-----Original Message-----
>From: Daniel Drake [mailto:drake at endlessm.com]
>Sent: Tuesday, September 12, 2017 12:20 PM
>To: Nath, Arindam <Arindam.Nath at amd.com>
>Cc: Joerg Roedel <joro at 8bytes.org>; Lendacky, Thomas
><Thomas.Lendacky at amd.com>; iommu at lists.linux-foundation.org; amd-
>gfx at lists.freedesktop.org; Deucher, Alexander
><Alexander.Deucher at amd.com>; Bridgman, John
><John.Bridgman at amd.com>; Suthikulpanit, Suravee
><Suravee.Suthikulpanit at amd.com>; linux at endlessm.com; Craig Stein
><stein12c at gmail.com>; michel at daenzer.net; Kuehling, Felix
><Felix.Kuehling at amd.com>; stable at vger.kernel.org
>Subject: Re: [PATCH] iommu/amd: flush IOTLB for specific domains only (v3)
>
>Hi,
>
>On Tue, May 30, 2017 at 3:38 PM, Nath, Arindam <Arindam.Nath at amd.com>
>wrote:
>>>-----Original Message-----
>>>From: Joerg Roedel [mailto:joro at 8bytes.org]
>>>Sent: Monday, May 29, 2017 8:09 PM
>>>To: Nath, Arindam <Arindam.Nath at amd.com>; Lendacky, Thomas
>>><Thomas.Lendacky at amd.com>
>>>Cc: iommu at lists.linux-foundation.org; amd-gfx at lists.freedesktop.org;
>>>Deucher, Alexander <Alexander.Deucher at amd.com>; Bridgman, John
>>><John.Bridgman at amd.com>; drake at endlessm.com; Suthikulpanit,
>Suravee
>>><Suravee.Suthikulpanit at amd.com>; linux at endlessm.com; Craig Stein
>>><stein12c at gmail.com>; michel at daenzer.net; Kuehling, Felix
>>><Felix.Kuehling at amd.com>; stable at vger.kernel.org
>>>Subject: Re: [PATCH] iommu/amd: flush IOTLB for specific domains only
>(v3)
>>>
>>>Hi Arindam,
>>>
>>>I met Tom Lendacky last week in Nuremberg last week and he told me he is
>>>working on the same area of the code that this patch is for. His reason
>>>for touching this code was to solve some locking problems. Maybe you two
>>>can work together on a joint approach to improve this?
>>
>> Sure Joerg, I will work with Tom.
>
>What was the end result here? I see that the code has been reworked in
>4.13 so your original patch no longer applies. Is the reworked version
>also expected to solve the original issue?

Yes, if the reworked patch resolves the issue, my patch won't be required anymore.

Thanks,
Arindam

>
>Thanks
>Daniel


More information about the amd-gfx mailing list