From: Dev Jain <dev.jain@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
akpm@linux-foundation.org, ljs@kernel.org
Cc: liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, kasong@tencent.com,
qi.zheng@linux.dev, shakeel.butt@linux.dev, baohua@kernel.org,
axelrasmussen@google.com, yuanchu@google.com, weixugc@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
riel@surriel.com, harry@kernel.org, jannh@google.com,
lance.yang@linux.dev, ryan.roberts@arm.com,
anshuman.khandual@arm.com
Subject: Re: [PATCH 1/3] mm/memory: move pte_install_uffd_wp_if_needed() into memory.c
Date: Thu, 16 Jul 2026 15:36:15 +0530 [thread overview]
Message-ID: <25bf1106-5739-4d54-8dac-7a5851d45b3d@arm.com> (raw)
In-Reply-To: <91231124-acd6-4b50-8d61-fa4e2e076649@kernel.org>
On 16/07/26 3:05 pm, David Hildenbrand (Arm) wrote:
> On 7/15/26 13:18, Dev Jain wrote:
>> pte_install_uffd_wp_if_needed() has grown too large for mm_inline.h.
>> Move it to memory.c.
>>
>> While at it, convert the comment to kerneldoc and rename the local
>> arguments from pte/pteval to ptep/pte so the pointer and pte value
>> are easier to distinguish.
>>
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>> ---
>> include/linux/mm.h | 2 ++
>> include/linux/mm_inline.h | 53 ----------------------------------
>> mm/memory.c | 60 +++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 62 insertions(+), 53 deletions(-)
>>
>> diff --git a/include/linux/mm.h b/include/linux/mm.h
>> index 550fb92957d18..a71341c44655e 100644
>> --- a/include/linux/mm.h
>> +++ b/include/linux/mm.h
>> @@ -5406,4 +5406,6 @@ void map_anon_folio_pte_nopf(struct folio *folio, pte_t *pte,
>> struct vm_area_struct *vma, unsigned long addr,
>> bool uffd_wp);
>>
>> +bool pte_install_uffd_wp_if_needed(struct vm_area_struct *vma,
>> + unsigned long addr, pte_t *ptep, pte_t pte);
>
> This could probably go to mm/internal.h instead?
>
> Apart from that LGTM.
Correct, I'll do that.
>
next prev parent reply other threads:[~2026-07-16 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:18 [PATCH 0/3] Batch unmap of uffd-wp file folios Dev Jain
2026-07-15 11:18 ` [PATCH 1/3] mm/memory: move pte_install_uffd_wp_if_needed() into memory.c Dev Jain
2026-07-16 9:35 ` David Hildenbrand (Arm)
2026-07-16 10:06 ` Dev Jain [this message]
2026-07-15 11:18 ` [PATCH 2/3] mm/memory: batch set uffd-wp markers during zapping Dev Jain
2026-07-16 9:41 ` David Hildenbrand (Arm)
2026-07-16 10:08 ` Dev Jain
2026-07-15 11:18 ` [PATCH 3/3] mm/rmap: batch unmap file folios belonging to uffd-wp VMAs Dev Jain
2026-07-16 9:44 ` David Hildenbrand (Arm)
2026-07-15 18:58 ` [PATCH 0/3] Batch unmap of uffd-wp file folios Andrew Morton
2026-07-16 4:57 ` Dev Jain
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=25bf1106-5739-4d54-8dac-7a5851d45b3d@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=david@kernel.org \
--cc=harry@kernel.org \
--cc=jannh@google.com \
--cc=kasong@tencent.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=yuanchu@google.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
all inboxes | Powered by JetHome®