From: Dev Jain <dev.jain@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
david@kernel.org, muchun.song@linux.dev, osalvador@suse.de,
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 v3 1/5] mm/rmap: convert page -> folio for hwpoison checks
Date: Sun, 26 Jul 2026 13:52:31 +0530 [thread overview]
Message-ID: <8001e108-62a7-452a-93ef-8e21416a0cd1@arm.com> (raw)
In-Reply-To: <20260725190721.f2e121f118ef817e42bb3874@linux-foundation.org>
On 26/07/26 7:37 am, Andrew Morton wrote:
> On Sat, 25 Jul 2026 13:06:25 +0530 Dev Jain <dev.jain@arm.com> wrote:
>
>>>> @@ -2204,7 +2205,11 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
>>>> /* Update high watermark before we lower rss */
>>>> update_hiwater_rss(mm);
>>>>
>>>> - if (PageHWPoison(subpage) && (flags & TTU_HWPOISON)) {
>>>> + /*
>>>> + * With TTU_HWPOISON, we only expect small folios or hugetlb
>>>> + * folios here for now.
>>>> + */
>>>> + if (folio_test_hwpoison(folio) && (flags & TTU_HWPOISON)) {
>>>
>>> As per v2 discussion, I feel this could be tightened up, maybe something like:
>>>
>>> /* unmap_poisoned_folio() only refs order-0 or hugetlb folios */
>>>
>>
>> I can do this. But note that this series is in mm-unstable already - what should
>> I base the v4 on?
>
> Ordinarily basing on latest Linus works. But this patchset has ~450
> patches ahead of it and a quick trial merge wasn't promising.
>
> I could drop the v3 series so you can base on next mm-new, please lmk.
>
> Or
>
> mm> git log --oneline | grep "mm/rmap: convert page -> folio for hwpoison checks"
> bb2f8a7eb126 mm/rmap: convert page -> folio for hwpoison checks
> mm> git checkout bb2f8a7eb126^
This one looks good, I'll do this.
I'll wait for Lorenzo's (or any others) potential review comments for two days
before I send this.
next prev parent reply other threads:[~2026-07-26 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 5:00 [PATCH v3 0/5] mm/rmap: Refactor try_to_unmap_one Dev Jain
2026-07-13 5:00 ` [PATCH v3 1/5] mm/rmap: convert page -> folio for hwpoison checks Dev Jain
2026-07-24 9:20 ` Lorenzo Stoakes (ARM)
2026-07-25 7:36 ` Dev Jain
2026-07-26 2:07 ` Andrew Morton
2026-07-26 8:22 ` Dev Jain [this message]
2026-07-13 5:00 ` [PATCH v3 2/5] mm/rmap: Add try_to_unmap_hugetlb_one Dev Jain
2026-07-24 10:39 ` Lorenzo Stoakes (ARM)
2026-07-25 8:47 ` Dev Jain
2026-07-13 5:00 ` [PATCH v3 3/5] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-07-13 5:00 ` [PATCH v3 4/5] mm/rmap: refactor anon folio unmap in try_to_unmap_one Dev Jain
2026-07-28 19:27 ` David Hildenbrand (Arm)
2026-07-13 5:00 ` [PATCH v3 5/5] mm/rmap: add anon folio unmap dispatcher 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=8001e108-62a7-452a-93ef-8e21416a0cd1@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
all inboxes | Powered by JetHome®