Hi, On Tue, May 30, 2017 at 3:38 PM, Nath, Arindam <arindam.n...@amd.com> wrote: >>-----Original Message----- >>From: Joerg Roedel [mailto:j...@8bytes.org] >>Sent: Monday, May 29, 2017 8:09 PM >>To: Nath, Arindam <arindam.n...@amd.com>; Lendacky, Thomas >><thomas.lenda...@amd.com> >>Cc: io...@lists.linux-foundation.org; amd-gfx@lists.freedesktop.org; >>Deucher, Alexander <alexander.deuc...@amd.com>; Bridgman, John >><john.bridg...@amd.com>; dr...@endlessm.com; Suthikulpanit, Suravee >><suravee.suthikulpa...@amd.com>; li...@endlessm.com; Craig Stein >><stein...@gmail.com>; mic...@daenzer.net; Kuehling, Felix >><felix.kuehl...@amd.com>; sta...@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? Thanks Daniel _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
