From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: alex.williamson@redhat.com, joro@8bytes.org, jroedel@suse.de
Subject: Re: [PATCH v4] vfio/type1: Adopt fast IOTLB flush interface when unmap IOVAs
Date: Thu, 1 Feb 2018 12:11:19 +0700 [thread overview]
Message-ID: <0fd4610a-c3ec-90f9-2d87-a7c2dd78193d@amd.com> (raw)
In-Reply-To: <1517391946-7830-1-git-send-email-suravee.suthikulpanit@amd.com>
Alex,
On 1/31/18 4:45 PM, Suravee Suthikulpanit wrote:
> Currently, VFIO IOMMU type1 unmaps IOVA pages synchronously, which requires
> IOTLB flush for every IOVA unmap. This results in a large number of IOTLB
> flushes during initialization of pass-through devices.
>
> This can be avoided using the asynchronous (fast) IOTLB flush interface.
>
> Cc: Alex Williamson<alex.williamson@redhat.com>
> Cc: Joerg Roedel<joro@8bytes.org>
> Signed-off-by: Suravee Suthikulpanit<suravee.suthikulpanit@amd.com>
> ---
>
> Changes from v3 (https://lkml.org/lkml/2018/1/21/244)
> * Refactor the code to unmap_unpin_fast() and unmap_unpin_slow()
> to improve code readability.
> * Fix logic in vfio_unmap_unpin() to fallback to unmap_unpin_slow()
> only for the failing iova unmapping, and continue the next unmapping
> with the unmap_unpin_fast(). (per Alex)
> * Fix error handling in case of failing to do fast unmapping to warn
> only once.
> * Remove reference to GPU in the commit message.
Please ignore v4. I found an issue in error handling logic. Also, I need to change
the return value back to size_t (as this was in a discussed in a separate thread).
Sorry for confusion. I'll clean up and send out v5.
Thanks,
Suravee
prev parent reply other threads:[~2018-02-01 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 9:45 Suravee Suthikulpanit
2018-02-01 5:11 ` Suravee Suthikulpanit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fd4610a-c3ec-90f9-2d87-a7c2dd78193d@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=alex.williamson@redhat.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®