Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
	akpm@linux-foundation.org, ljs@kernel.org, muchun.song@linux.dev,
	osalvador@suse.de
Cc: riel@surriel.com, liam@infradead.org, vbabka@kernel.org,
	harry@kernel.org, jannh@google.com, lance.yang@linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v2 2/5] mm/rmap: Add try_to_unmap_hugetlb_one
Date: Mon, 13 Jul 2026 17:41:57 +0530	[thread overview]
Message-ID: <de714ba1-2d97-4403-bd80-6de914500461@arm.com> (raw)
In-Reply-To: <db3c6f52-7a82-4afa-9720-1edf2f5c855d@kernel.org>



On 13/07/26 4:04 pm, David Hildenbrand (Arm) wrote:
> On 7/10/26 15:16, Dev Jain wrote:
>>
>>
>> On 10/07/26 11:29 am, Dev Jain wrote:
>>> Simplify try_to_unmap_one() by separating the hugetlb parts into
>>> try_to_unmap_hugetlb_one().
>>>
>>> To understand the correctness of the refactoring, the following points
>>> are noted:
>>>
>>> 1. try_to_unmap() is called for hugetlb folios only when they are
>>>    hwpoisoned.
>>>
>>> 2. A hugetlb VMA cannot be mlocked.
>>>
>>> 3. page_vma_mapped_walk() returns at most one hugetlb mapping in a VMA,
>>>    and that mapping points at the head PFN.
>>>
>>> 4. We won't ever process a softleaf entry that encodes a hugetlb folio;
>>>    hugetlb folios are never swapped out, migration entries will be
>>>    skipped (PVMW_MIGRATION not passed), and device-exclusive does not
>>>    work for hugetlb.
>>>
>>> 5. The hwpoison entry is constructed from the poisoned folio, just as in
>>>    the pre-refactor code. Any previous uffd-wp state is deliberately not
>>>    preserved for the hwpoison entry.
>>>
>>> 6. TTU_HWPOISON is always present; for it to not be present, either the
>>>    folio has to be in swapcache, or mapping_can_writeback() is true (see
>>>    unmap_poisoned_folio), none of which is true for hugetlb folios.
>>>
>>> 7. Hugetlb uses separate counters from normal rss counters, therefore
>>>    update_highwater_rss() need not be called.
>>>
>>> While at it:
>>>
>>>  - Change VM_BUG_* to VM_WARN_*.
>>>
>>>  - Do not declare variables which are only used once.
>>>
>>>  - Constify some variables.
>>>
>>>  - Add some more VM_WARN_* to assert some invariants.
>>>
>>> Except the above 4 points, no functional change intended.
>>>
>>> Suggested-by: David Hildenbrand (Arm) <david@kernel.org>
>>> Acked-by: David Hildenbrand (Arm) <david@kernel.org>
>>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>>> ---
>>
>> Andrew, could you squash the following diff:
>>
>> diff --git a/mm/rmap.c b/mm/rmap.c
>> index cf02b315a2ead..b61051b879c4c 100644
>> --- a/mm/rmap.c
>> +++ b/mm/rmap.c
>> @@ -2229,8 +2229,7 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
>>                 update_hiwater_rss(mm);
>>
>>                 /*
>> -                * With TTU_HWPOISON, we only expect small folios or hugetlb
>> -                * folios here for now.
>> +                * With TTU_HWPOISON, we only expect small folios here.
>>                  */
>>                 if (folio_test_hwpoison(folio) && (flags & TTU_HWPOISON)) {
>>                         pteval = swp_entry_to_pte(make_hwpoison_entry(subpage));
> 
> Note that the comment likely fits into a single line now.

Yes, took care of that in v3 :)


> 



  reply	other threads:[~2026-07-13 12:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  5:59 [PATCH v2 0/5] mm/rmap: Refactor try_to_unmap_one Dev Jain
2026-07-10  5:59 ` [PATCH v2 1/5] mm/rmap: convert page -> folio for hwpoison checks Dev Jain
2026-07-10 12:22   ` David Hildenbrand (Arm)
2026-07-10 13:14     ` Dev Jain
2026-07-10  5:59 ` [PATCH v2 2/5] mm/rmap: Add try_to_unmap_hugetlb_one Dev Jain
2026-07-10 13:16   ` Dev Jain
2026-07-13 10:34     ` David Hildenbrand (Arm)
2026-07-13 12:11       ` Dev Jain [this message]
2026-07-10  5:59 ` [PATCH v2 3/5] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-07-10  5:59 ` [PATCH v2 4/5] mm/rmap: refactor anon folio unmap in try_to_unmap_one Dev Jain
2026-07-10  5:59 ` [PATCH v2 5/5] mm/rmap: add anon folio unmap dispatcher Dev Jain
2026-07-10 12:27   ` David Hildenbrand (Arm)
2026-07-10 13:13     ` Dev Jain
2026-07-11  0:35       ` Andrew Morton
2026-07-11 12:14         ` Dev Jain
2026-07-12 11:47         ` David Hildenbrand (Arm)

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=de714ba1-2d97-4403-bd80-6de914500461@arm.com \
    --to=dev.jain@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=david@kernel.org \
    --cc=harry@kernel.org \
    --cc=jannh@google.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=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=riel@surriel.com \
    --cc=ryan.roberts@arm.com \
    --cc=vbabka@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