From: David Hildenbrand <david@redhat.com>
To: lizhe.67@bytedance.com, alex.williamson@redhat.com,
akpm@linux-foundation.org, peterx@redhat.com, jgg@ziepe.ca
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 2/5] vfio/type1: optimize vfio_pin_pages_remote()
Date: Fri, 4 Jul 2025 10:41:41 +0200 [thread overview]
Message-ID: <8806f687-12e4-4456-a7b6-ecdc5adc9f2e@redhat.com> (raw)
In-Reply-To: <20250704062602.33500-3-lizhe.67@bytedance.com>
> * Attempt to pin pages. We really don't want to track all the pfns and
> * the iommu can only map chunks of consecutive pfns anyway, so get the
> @@ -680,32 +724,47 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr,
> * and rsvd here, and therefore continues to use the batch.
> */
> while (true) {
> + long nr_pages, acct_pages = 0;
> +
> if (pfn != *pfn_base + pinned ||
> rsvd != is_invalid_reserved_pfn(pfn))
> goto out;
>
> + /*
> + * Using GUP with the FOLL_LONGTERM in
> + * vaddr_get_pfns() will not return invalid
> + * or reserved pages.
> + */
> + nr_pages = num_pages_contiguous(
> + &batch->pages[batch->offset],
> + batch->size);
> + if (!rsvd) {
> + acct_pages = nr_pages;
> + acct_pages -= vpfn_pages(dma, iova, nr_pages);
I'm not familiar with the vpfn_pages() part, but the other stuff LGTM.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-04 8:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 6:25 [PATCH v2 0/5] vfio/type1: optimize vfio_pin_pages_remote() and vfio_unpin_pages_remote() lizhe.67
2025-07-04 6:25 ` [PATCH v2 1/5] mm: introduce num_pages_contiguous() lizhe.67
2025-07-04 7:56 ` David Hildenbrand
2025-07-04 8:21 ` lizhe.67
2025-07-04 17:10 ` Jason Gunthorpe
2025-07-07 3:38 ` lizhe.67
2025-07-04 21:19 ` kernel test robot
2025-07-07 3:52 ` lizhe.67
2025-07-04 6:25 ` [PATCH v2 2/5] vfio/type1: optimize vfio_pin_pages_remote() lizhe.67
2025-07-04 8:41 ` David Hildenbrand [this message]
2025-07-04 6:26 ` [PATCH v2 3/5] vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() lizhe.67
2025-07-04 6:26 ` [PATCH v2 4/5] vfio/type1: introduce a new member has_rsvd for struct vfio_dma lizhe.67
2025-07-04 8:46 ` David Hildenbrand
2025-07-04 6:26 ` [PATCH v2 5/5] vfio/type1: optimize vfio_unpin_pages_remote() lizhe.67
2025-07-04 8:47 ` David Hildenbrand
2025-07-04 17:11 ` Jason Gunthorpe
2025-07-07 3:44 ` lizhe.67
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=8806f687-12e4-4456-a7b6-ecdc5adc9f2e@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhe.67@bytedance.com \
--cc=peterx@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;
as well as URLs for NNTP newsgroup(s).