From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: linux-next@vger.kernel.org, akpm@linux-foundation.org,
jack@suse.cz, kirill@shutemov.name
Cc: borntraeger@de.ibm.com, david@redhat.com, aarcange@redhat.com,
linux-mm@kvack.org, frankja@linux.ibm.com, sfr@canb.auug.org.au,
jhubbard@nvidia.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: [PATCH v4 0/2] add callbacks for inaccessible pages
Date: Fri, 6 Mar 2020 14:25:35 +0100 [thread overview]
Message-ID: <20200306132537.783769-1-imbrenda@linux.ibm.com> (raw)
This patchset has a fixup for gup/mm, and provides the necessary arch
hooks to enable protected virtualization.
Andrew: please simply squash/fixup the first patch into the appropriate
one that is already in your tree.
v3-> v4:
* changed WARN_ON into VM_BUG_ON_PAGE as per review,
* and small improvement of the associated comment
v2 -> v3:
* revert some cosmetic changes to improve readability
* improve some comments
v1 -> v2:
* use put_compound_head in the first patch
* fix commit message of the second patch
* minor code cleanups
* some comments to explain why sometimes we are not doing things
Claudio Imbrenda (2):
mm/gup: fixup for 9947ea2c1e608e32 "mm/gup: track FOLL_PIN pages"
mm/gup/writeback: add callbacks for inaccessible pages
include/linux/gfp.h | 6 ++++
mm/gup.c | 76 +++++++++++++++++++++++++++++----------------
mm/page-writeback.c | 9 +++++-
3 files changed, 64 insertions(+), 27 deletions(-)
--
2.24.1
next reply other threads:[~2020-03-06 13:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 13:25 Claudio Imbrenda [this message]
2020-03-06 13:25 ` [PATCH v4 1/2] mm/gup: fixup for 9947ea2c1e608e32 "mm/gup: track FOLL_PIN pages" Claudio Imbrenda
2020-03-06 13:25 ` [PATCH v4 2/2] mm/gup/writeback: add callbacks for inaccessible pages Claudio Imbrenda
2020-04-13 20:22 ` Dave Hansen
2020-04-14 16:03 ` Claudio Imbrenda
2020-04-14 18:50 ` Dave Hansen
2020-04-15 9:26 ` Claudio Imbrenda
2020-04-15 11:39 ` Janosch Frank
2020-04-15 21:52 ` Dave Hansen
2020-04-15 22:17 ` Peter Zijlstra
2020-04-15 23:34 ` Dave Hansen
2020-04-16 12:15 ` Claudio Imbrenda
2020-04-16 14:20 ` Dave Hansen
2020-04-16 14:59 ` Claudio Imbrenda
2020-04-16 15:36 ` Dave Hansen
2020-04-16 16:34 ` Claudio Imbrenda
2020-04-16 19:02 ` Dave Hansen
2020-04-21 21:31 ` Dave Hansen
2020-04-28 19:43 ` Dave Hansen
2020-04-28 20:02 ` Christian Borntraeger
2020-04-28 23:39 ` Claudio Imbrenda
2020-04-29 0:42 ` Dave Hansen
2020-04-16 11:51 ` Claudio Imbrenda
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=20200306132537.783769-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.