All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/2] mm/gup: introduce pin_user_pages_locked(), use it in frame_vector.c
Date: Wed, 27 May 2020 15:32:41 -0700	[thread overview]
Message-ID: <20200527223243.884385-1-jhubbard@nvidia.com> (raw)

Hi,

This applies on top of the pin_user_pages_unlocked() patch that I sent
earlier [1].

This adds yet one more pin_user_pages*() variant, and uses that to
convert mm/frame_vector.c.

With this, along with maybe 20 or 30 other recent patches in various
trees, we are close to having the relevant gup call sites
converted--with the notable exception of the bio/block layer.


[1] https://lore.kernel.org/r/20200518012157.1178336-2-jhubbard@nvidia.com

John Hubbard (2):
  mm/gup: introduce pin_user_pages_locked()
  mm/gup: frame_vector: convert get_user_pages() --> pin_user_pages()

 include/linux/mm.h |  2 ++
 mm/frame_vector.c  |  7 +++----
 mm/gup.c           | 30 ++++++++++++++++++++++++++++++
 3 files changed, 35 insertions(+), 4 deletions(-)


base-commit: 9cb1fd0efd195590b828b9b865421ad345a4a145
-- 
2.26.2


             reply	other threads:[~2020-05-27 22:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 22:32 John Hubbard [this message]
2020-05-27 22:32 ` [PATCH 1/2] mm/gup: introduce pin_user_pages_locked() John Hubbard
2020-05-28  8:43   ` David Hildenbrand
2020-05-31  7:04   ` Souptick Joarder
2020-05-31  7:04     ` Souptick Joarder
2020-05-31  7:13     ` Souptick Joarder
2020-05-31  7:13       ` Souptick Joarder
2020-05-31 19:56       ` John Hubbard
2020-05-31 19:52     ` John Hubbard
2020-05-31 13:03   ` Pankaj Gupta
2020-05-31 13:03     ` Pankaj Gupta
2020-05-27 22:32 ` [PATCH 2/2] mm/gup: frame_vector: convert get_user_pages() --> pin_user_pages() John Hubbard
2020-05-28  8:46   ` David Hildenbrand

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=20200527223243.884385-1-jhubbard@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.