From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-mm@kvack.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH 1/3] mm: Use arch_make_folio_accessible() in gup_pte_range()
Date: Fri, 15 Sep 2023 18:28:26 +0100 [thread overview]
Message-ID: <20230915172829.2632994-2-willy@infradead.org> (raw)
In-Reply-To: <20230915172829.2632994-1-willy@infradead.org>
This function already uses folios, so convert the
arch_make_page_accessible() call to arch_make_folio_accessible().
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
---
mm/gup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/gup.c b/mm/gup.c
index 2f8a2d89fde1..ab8a0ebc728e 100644
--- a/mm/gup.c
+++ b/mm/gup.c
@@ -2622,13 +2622,13 @@ static int gup_pte_range(pmd_t pmd, pmd_t *pmdp, unsigned long addr,
}
/*
- * We need to make the page accessible if and only if we are
+ * We need to make the folio accessible if and only if we are
* going to access its content (the FOLL_PIN case). Please
* see Documentation/core-api/pin_user_pages.rst for
* details.
*/
if (flags & FOLL_PIN) {
- ret = arch_make_page_accessible(page);
+ ret = arch_make_folio_accessible(folio);
if (ret) {
gup_put_folio(folio, 1, flags);
goto pte_unmap;
--
2.40.1
next prev parent reply other threads:[~2023-09-15 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 17:28 [PATCH 0/3] Use arch_make_folio_accessible() everywhere Matthew Wilcox (Oracle)
2023-09-15 17:28 ` Matthew Wilcox (Oracle) [this message]
2023-09-15 17:28 ` [PATCH 2/3] mm: Convert follow_page_pte() to use a folio Matthew Wilcox (Oracle)
2023-09-15 17:28 ` [PATCH 3/3] s390: Convert arch_make_page_accessible() to arch_make_folio_accessible() Matthew Wilcox (Oracle)
2023-09-15 17:54 ` [PATCH 0/3] Use arch_make_folio_accessible() everywhere Claudio Imbrenda
2023-09-15 18:17 ` Matthew Wilcox
2023-09-18 11:01 ` 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=20230915172829.2632994-2-willy@infradead.org \
--to=willy@infradead.org \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.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 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).