From: Jason Gunthorpe <jgg@nvidia.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
iommu@lists.linux.dev, Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, Kevin Tian <kevin.tian@intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 2/7] mm/gup: remove unused vmas parameter from pin_user_pages_remote()
Date: Mon, 17 Apr 2023 10:02:25 -0300 [thread overview]
Message-ID: <ZD1DYVHIHxkN98PL@nvidia.com> (raw)
In-Reply-To: <c75291e4afe968824b89831cbd341f8b54ce28a4.1681508038.git.lstoakes@gmail.com>
On Sat, Apr 15, 2023 at 12:27:23AM +0100, Lorenzo Stoakes wrote:
> No invocation of pin_user_pages_remote() uses the vmas parameter, so remove
> it. This forms part of a larger patch set eliminating the use of the vmas
> parameters altogether.
>
> Signed-off-by: Lorenzo Stoakes <lstoakes@gmail.com>
> ---
> drivers/iommu/iommufd/pages.c | 4 ++--
> drivers/vfio/vfio_iommu_type1.c | 2 +-
> include/linux/mm.h | 2 +-
> mm/gup.c | 8 +++-----
> mm/process_vm_access.c | 2 +-
> 5 files changed, 8 insertions(+), 10 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
next prev parent reply other threads:[~2023-04-17 13:02 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 23:25 [PATCH 0/7] remove the vmas parameter from GUP APIs Lorenzo Stoakes
2023-04-14 23:27 ` [PATCH 1/7] mm/gup: remove unused vmas parameter from get_user_pages() Lorenzo Stoakes
2023-04-14 23:27 ` Lorenzo Stoakes
2023-04-14 23:27 ` Lorenzo Stoakes
2023-04-15 5:27 ` Greg Kroah-Hartman
2023-04-15 5:27 ` Greg Kroah-Hartman
2023-04-15 5:27 ` Greg Kroah-Hartman
2023-04-17 13:01 ` Jason Gunthorpe
2023-04-17 13:01 ` Jason Gunthorpe
2023-04-17 13:01 ` Jason Gunthorpe
2023-04-14 23:27 ` [PATCH 2/7] mm/gup: remove unused vmas parameter from pin_user_pages_remote() Lorenzo Stoakes
2023-04-17 13:02 ` Jason Gunthorpe [this message]
2023-04-14 23:27 ` [PATCH 3/7] mm/gup: remove vmas parameter from get_user_pages_remote() Lorenzo Stoakes
2023-04-14 23:27 ` Lorenzo Stoakes
2023-04-15 0:25 ` Tetsuo Handa
2023-04-15 8:11 ` Lorenzo Stoakes
2023-04-17 13:09 ` Jason Gunthorpe
2023-04-17 13:09 ` Jason Gunthorpe
2023-04-17 13:13 ` Lorenzo Stoakes
2023-04-17 13:13 ` Lorenzo Stoakes
2023-04-17 13:16 ` Jason Gunthorpe
2023-04-17 13:16 ` Jason Gunthorpe
2023-04-17 13:23 ` Lorenzo Stoakes
2023-04-17 13:23 ` Lorenzo Stoakes
2023-04-17 15:07 ` Eric W. Biederman
2023-04-17 15:07 ` Eric W. Biederman
2023-04-17 15:14 ` Lorenzo Stoakes
2023-04-17 15:14 ` Lorenzo Stoakes
2023-04-14 23:27 ` [PATCH 4/7] mm/gup: introduce the FOLL_SAME_FILE GUP flag Lorenzo Stoakes
2023-04-17 13:14 ` Jason Gunthorpe
2023-04-17 13:25 ` Lorenzo Stoakes
2023-04-17 13:27 ` Jason Gunthorpe
2023-04-14 23:27 ` [PATCH 5/7] io_uring: rsrc: use FOLL_SAME_FILE on pin_user_pages() Lorenzo Stoakes
2023-04-17 12:56 ` Jason Gunthorpe
2023-04-17 13:19 ` Lorenzo Stoakes
2023-04-17 13:26 ` Jason Gunthorpe
2023-04-17 14:00 ` Lorenzo Stoakes
2023-04-17 14:15 ` Jason Gunthorpe
2023-04-17 15:20 ` Lorenzo Stoakes
2023-04-17 19:00 ` Lorenzo Stoakes
2023-04-17 19:24 ` Jason Gunthorpe
2023-04-17 19:45 ` Lorenzo Stoakes
2023-04-18 16:25 ` Pavel Begunkov
2023-04-18 16:35 ` Pavel Begunkov
2023-04-18 16:36 ` Jason Gunthorpe
2023-04-18 17:25 ` Pavel Begunkov
2023-04-18 18:19 ` Jason Gunthorpe
2023-04-14 23:27 ` [PATCH 6/7] mm/gup: remove vmas parameter from pin_user_pages() Lorenzo Stoakes
2023-04-14 23:27 ` Lorenzo Stoakes
2023-04-14 23:27 ` [PATCH 7/7] mm/gup: remove vmas array from internal GUP functions Lorenzo Stoakes
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=ZD1DYVHIHxkN98PL@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=david@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.