From: Kirti Wankhede <kwankhede@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>, <kvm@vger.kernel.org>
Cc: <eric.auger@redhat.com>, <peterx@redhat.com>,
<linux-kernel@vger.kernel.org>, <slp@redhat.com>
Subject: Re: [PATCH v4 2/2] vfio/type1: Prune vfio_pin_page_external()
Date: Tue, 18 Apr 2017 00:46:51 +0530 [thread overview]
Message-ID: <16f06e1b-ea0f-0b50-d083-aba77a496c5f@nvidia.com> (raw)
In-Reply-To: <20170417014239.25866.42333.stgit@gimli.home>
On 4/17/2017 7:12 AM, Alex Williamson wrote:
> With vfio_lock_acct() testing the locked memory limit under mmap_sem,
> it's redundant to do it here for a single page. We can also reorder
> our tests such that we can avoid testing for reserved pages if we're
> not doing accounting, and test the process CAP_IPC_LOCK only if we
> are doing accounting. Finally, this function oddly returns 1 on
> success. Update to return zero on success, -errno on error. Since
> the function only pins a single page, there's no need to return the
> number of pages pinned.
>
> N.B. vfio_pin_pages_remote() can pin a large contiguous range of pages
> before calling vfio_lock_acct(). If we were to similarly remove the
> extra test there, a user could temporarily pin far more pages than
> they're allowed.
>
> Suggested-by: Kirti Wankhede <kwankhede@nvidia.com>
> Suggested-by: Peter Xu <peterx@redhat.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 34 +++++-----------------------------
> 1 file changed, 5 insertions(+), 29 deletions(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index fb18e4a5df62..07e0e58f22e9 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -479,43 +479,21 @@ static long vfio_unpin_pages_remote(struct vfio_dma *dma, dma_addr_t iova,
> static int vfio_pin_page_external(struct vfio_dma *dma, unsigned long vaddr,
> unsigned long *pfn_base, bool do_accounting)
> {
> - unsigned long limit;
> - bool lock_cap = has_capability(dma->task, CAP_IPC_LOCK);
> struct mm_struct *mm;
> int ret;
> - bool rsvd;
>
> mm = get_task_mm(dma->task);
> if (!mm)
> return -ENODEV;
>
> ret = vaddr_get_pfn(mm, vaddr, dma->prot, pfn_base);
> - if (ret)
> - goto pin_page_exit;
> -
> - rsvd = is_invalid_reserved_pfn(*pfn_base);
> - limit = task_rlimit(dma->task, RLIMIT_MEMLOCK) >> PAGE_SHIFT;
> -
> - if (!rsvd && !lock_cap && mm->locked_vm + 1 > limit) {
> - put_pfn(*pfn_base, dma->prot);
> - pr_warn("%s: Task %s (%d) RLIMIT_MEMLOCK (%ld) exceeded\n",
> - __func__, dma->task->comm, task_pid_nr(dma->task),
> - limit << PAGE_SHIFT);
> - ret = -ENOMEM;
> - goto pin_page_exit;
> - }
> -
> - if (!rsvd && do_accounting) {
> - ret = vfio_lock_acct(dma->task, 1, lock_cap);
> - if (ret) {
> + if (!ret && do_accounting && !is_invalid_reserved_pfn(*pfn_base)) {
> + ret = vfio_lock_acct(dma->task, 1,
> + has_capability(dma->task, CAP_IPC_LOCK));
> + if (ret)
> put_pfn(*pfn_base, dma->prot);
> - goto pin_page_exit;
> - }
> }
>
> - ret = 1;
> -
> -pin_page_exit:
> mmput(mm);
> return ret;
> }
Thanks. This looks clean.
Just a nit pick, if vfio_lock_acct() returns -ENOMEM, its better to have
warning about task's mlock limit exceeded, which got removed in the
cleanup. No need to review again.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Thanks,
Kirti
> @@ -595,10 +573,8 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,
> remote_vaddr = dma->vaddr + iova - dma->iova;
> ret = vfio_pin_page_external(dma, remote_vaddr, &phys_pfn[i],
> do_accounting);
> - if (ret <= 0) {
> - WARN_ON(!ret);
> + if (ret)
> goto pin_unwind;
> - }
>
> ret = vfio_add_to_pfn_list(dma, iova, phys_pfn[i]);
> if (ret) {
>
prev parent reply other threads:[~2017-04-17 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 1:42 [PATCH v4 0/2] vfio/type1: Synchronous locked page accounting Alex Williamson
2017-04-17 1:42 ` [PATCH v4 1/2] vfio/type1: Remove locked page accounting workqueue Alex Williamson
2017-04-17 6:47 ` Peter Xu
2017-04-17 14:32 ` Alex Williamson
2017-04-17 19:05 ` Kirti Wankhede
2017-04-17 19:19 ` Alex Williamson
2017-04-17 19:32 ` Kirti Wankhede
2017-04-17 21:32 ` Alex Williamson
2017-04-18 2:54 ` Peter Xu
2017-04-18 18:21 ` Kirti Wankhede
2017-04-17 1:42 ` [PATCH v4 2/2] vfio/type1: Prune vfio_pin_page_external() Alex Williamson
2017-04-17 6:54 ` Peter Xu
2017-04-17 17:20 ` Alex Williamson
2017-04-17 19:16 ` Kirti Wankhede [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=16f06e1b-ea0f-0b50-d083-aba77a496c5f@nvidia.com \
--to=kwankhede@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=slp@redhat.com \
/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
Powered by JetHome