From: "Garg, Shivank" <shivankg@amd.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
willy@infradead.org, Matthew Brost <matthew.brost@intel.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Rakie Kim <rakie.kim@sk.com>, Byungchul Park <byungchul@sk.com>,
Gregory Price <gourry@gourry.net>,
Ying Huang <ying.huang@linux.alibaba.com>,
Alistair Popple <apopple@nvidia.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/migrate: rename PAGE_ migration flags to FOLIO_
Date: Wed, 25 Mar 2026 00:33:44 +0530 [thread overview]
Message-ID: <c18bb671-ad0d-43d8-91b0-afc246c924a4@amd.com> (raw)
In-Reply-To: <54398FC0-2F68-410C-B9C4-2802810C119B@nvidia.com>
On 3/24/2026 7:08 PM, Zi Yan wrote:
> On 24 Mar 2026, at 7:47, Shivank Garg wrote:
>
>> These flags only track folio-specific state during migration and are
>> not used for movable_ops pages. Rename the enum values and the
>> old_page_state variable to match.
>>
>> No functional change.
>>
>> Suggested-by: David Hildenbrand <david@kernel.org>
>> Signed-off-by: Shivank Garg <shivankg@amd.com>
>> ---
>>
>> Applies cleanly on mm-new (02b045682c74).
>>
>> v1: https://lore.kernel.org/all/20260323141935.389232-3-shivankg@amd.com
>>
>> v2:
>> - Rename FOLIO_MF_* to FOLIO_*, per feedback from Willy.
>>
>> mm/migrate.c | 46 +++++++++++++++++++++++-----------------------
>> 1 file changed, 23 insertions(+), 23 deletions(-)
>>
>> diff --git a/mm/migrate.c b/mm/migrate.c
>> index 05cb408846f2..7dd6c2f2e1ef 100644
>> --- a/mm/migrate.c
>> +++ b/mm/migrate.c
>> @@ -1135,26 +1135,26 @@ static int move_to_new_folio(struct folio *dst, struct folio *src,
>> * This is safe because nobody is using it except us.
>> */
>> enum {
>> - PAGE_WAS_MAPPED = BIT(0),
>> - PAGE_WAS_MLOCKED = BIT(1),
>> - PAGE_OLD_STATES = PAGE_WAS_MAPPED | PAGE_WAS_MLOCKED,
>> + FOLIO_WAS_MAPPED = BIT(0),
>> + FOLIO_WAS_MLOCKED = BIT(1),
>> + FOLIO_OLD_STATES = FOLIO_WAS_MAPPED | FOLIO_WAS_MLOCKED,
>> };
>>
>> static void __migrate_folio_record(struct folio *dst,
>> - int old_page_state,
>> + int old_folio_state,
>> struct anon_vma *anon_vma)
>> {
>> - dst->private = (void *)anon_vma + old_page_state;
>> + dst->private = (void *)anon_vma + old_folio_state;
>> }
>>
>> static void __migrate_folio_extract(struct folio *dst,
>> - int *old_page_state,
>> + int *old_folio_state,
>> struct anon_vma **anon_vmap)
>> {
>> unsigned long private = (unsigned long)dst->private;
>>
>> - *anon_vmap = (struct anon_vma *)(private & ~PAGE_OLD_STATES);
>> - *old_page_state = private & PAGE_OLD_STATES;
>> + *anon_vmap = (struct anon_vma *)(private & ~FOLIO_OLD_STATES);
>> + *old_folio_state = private & FOLIO_OLD_STATES;
>> dst->private = NULL;
>> }
>
> Just an observation on folio->private, it is void*, but page->private
> is unsigned long. It confused me a bit. There are folio_get_private()
> and folio_change_private(), I wonder if we want to use them here
> instead of direct ->private accesses. Feel free to ignore this,
> since it is irrelevant to this patch.
>
Yeah, using folio_get_private() and folio_change_private() would be cleaner.
I'll keep it in mind as a follow-up cleanup but leaving this patch as a pure rename for now.
Thanks for suggestion.
> LGTM.
>
> Reviewed-by: Zi Yan <ziy@nvidia.com>
Thank you :)
Best regards,
Shivank
next prev parent reply other threads:[~2026-03-24 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 11:47 Shivank Garg
2026-03-24 12:31 ` David Hildenbrand (Arm)
2026-03-24 18:59 ` Garg, Shivank
2026-03-24 13:38 ` Zi Yan
2026-03-24 19:03 ` Garg, Shivank [this message]
2026-03-25 9:21 ` Garg, Shivank
2026-03-25 9:25 ` David Hildenbrand (Arm)
2026-03-25 11:04 ` Garg, Shivank
2026-03-25 14:21 ` Zi Yan
2026-03-25 14:53 ` David Hildenbrand (Arm)
2026-03-25 15:00 ` Zi Yan
2026-03-25 15:04 ` David Hildenbrand (Arm)
2026-03-25 15:05 ` Zi Yan
2026-03-25 15:28 ` Matthew Wilcox
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=c18bb671-ad0d-43d8-91b0-afc246c924a4@amd.com \
--to=shivankg@amd.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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