Hi Alex,
On 11/18/17 4:51 AM, Alex Williamson wrote:
> On Fri, 17 Nov 2017 15:11:19 -0600
> Suravee Suthikulpanit<[email protected]> wrote:
>
>> From: Suravee Suthikulpanit<[email protected]>
>>
>> VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
>> IOTLB flushing for every unmapping. This results in large IOTLB flushing
>> overhead when handling pass-through devices with a large number of mapped
>> IOVAs (e.g. GPUs).
> Of course the type of device is really irrelevant, QEMU maps the entire
> VM address space for any assigned device.
Right, in this case certain high performance dGPUs map large address space.
>
>> This can be avoided by using the new IOTLB flushing interface.
>>
>> Cc: Alex Williamson<[email protected]>
>> Cc: Joerg Roedel<[email protected]>
>> Signed-off-by: Suravee Suthikulpanit<[email protected]>
>> ---
>> drivers/vfio/vfio_iommu_type1.c | 12 +++++++++---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
>> index 92155cc..28a7ab6 100644
>> --- a/drivers/vfio/vfio_iommu_type1.c
>> +++ b/drivers/vfio/vfio_iommu_type1.c
>> @@ -698,10 +698,12 @@ static long vfio_unmap_unpin(struct vfio_iommu *iommu, struct vfio_dma *dma,
>> break;
>> }
>>
>> - unmapped = iommu_unmap(domain->domain, iova, len);
>> + unmapped = iommu_unmap_fast(domain->domain, iova, len);
>> if (WARN_ON(!unmapped))
>> break;
>>
>> + iommu_tlb_range_add(domain->domain, iova, len);
>> +
> We should only add @unmapped, not @len, right?
Hm right, I will change this in V2.
Thanks,
Suravee
From 1584455842194466694@xxx Sun Nov 19 01:27:22 +0000 2017
X-GM-THRID: 1584393640782294553
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread