From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
Ye Liu <ye.liu@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: Zi Yan <ziy@nvidia.com>, 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>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/9] mm/page_owner: add MR_NEVER to enum migrate_reason and use it for last_migrate_reason
Date: Tue, 14 Jul 2026 15:22:06 +0200 [thread overview]
Message-ID: <9e9345c8-30a4-4f78-ba55-d7fa073b82d5@kernel.org> (raw)
In-Reply-To: <037d58c6-de55-4b69-bb71-905e03985657@kernel.org>
On 7/14/26 15:09, Vlastimil Babka (SUSE) wrote:
> On 7/14/26 15:05, David Hildenbrand (Arm) wrote:
>> On 7/14/26 03:51, Ye Liu wrote:
>>> The last_migrate_reason field uses -1 as a sentinel value to mean "no
>>> migration has happened". Replace the four bare -1 occurrences by
>>> adding a proper MR_NEVER member to enum migrate_reason, defining a
>>> corresponding "never_migrated" string in the MIGRATE_REASON trace
>>> macro, and updating the GDB page_owner script to use MR_NEVER instead
>>> of the hardcoded -1 so that lx-dump-page-owner does not incorrectly
>>> report unmigrated pages as migrated.
>>>
>>> No functional change.
>>>
>>> Signed-off-by: Ye Liu <ye.liu@linux.dev>
>>> Reviewed-by: Zi Yan <ziy@nvidia.com>
>>> Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
>>> ---
>>> include/linux/migrate_mode.h | 1 +
>>> include/trace/events/migrate.h | 3 ++-
>>> mm/page_owner.c | 8 ++++----
>>> scripts/gdb/linux/page_owner.py | 4 +++-
>>> 4 files changed, 10 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/include/linux/migrate_mode.h b/include/linux/migrate_mode.h
>>> index 265c4328b36a..05102d4d2490 100644
>>> --- a/include/linux/migrate_mode.h
>>> +++ b/include/linux/migrate_mode.h
>>> @@ -25,6 +25,7 @@ enum migrate_reason {
>>> MR_LONGTERM_PIN,
>>> MR_DEMOTION,
>>> MR_DAMON,
>>> + MR_NEVER, /* page has never been migrated */
>>
>> Shouldn't this be more like
>>
>> "MR_NONE" ?
>>
>> As "never" is not really a "reason" ?
>
> It's not used ever as a reason that would be actually passed to migration.
Right, it's a placeholder for "there is no migrate reason because it is unset"
> So I think the name is more descriptive this way.
Not sure I agree. The usual translation of -1 -> unset is NONE or UNSET.
At least I was confused by "NEVER".
--
Cheers,
David
next prev parent reply other threads:[~2026-07-14 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 1:50 [PATCH v6 0/9] mm/page_owner: misc cleanups Ye Liu
2026-07-14 1:51 ` [PATCH v6 1/9] mm/page_owner: extract skip_buddy_pages() helper to unify buddy page skipping Ye Liu
2026-07-14 1:51 ` [PATCH v6 2/9] mm/page_owner: add MR_NEVER to enum migrate_reason and use it for last_migrate_reason Ye Liu
2026-07-14 13:05 ` David Hildenbrand (Arm)
2026-07-14 13:09 ` Vlastimil Babka (SUSE)
2026-07-14 13:22 ` David Hildenbrand (Arm) [this message]
2026-07-14 13:49 ` Vlastimil Babka (SUSE)
2026-07-14 14:44 ` David Hildenbrand (Arm)
2026-07-14 1:51 ` [PATCH v6 3/9] mm: use enum migrate_reason instead of int for migration reason parameters Ye Liu
2026-07-14 13:07 ` David Hildenbrand (Arm)
2026-07-14 1:51 ` [PATCH v6 4/9] mm/page_owner: hoist CONFIG_MEMCG to function level for print_page_owner_memcg() Ye Liu
2026-07-14 1:51 ` [PATCH v6 5/9] mm/page_owner: add missing newline to count_threshold format string Ye Liu
2026-07-14 1:51 ` [PATCH v6 6/9] mm/page_owner: move free_ts_nsec output to free section in __dump_page_owner() Ye Liu
2026-07-14 1:51 ` [PATCH v6 7/9] mm/page_owner: drop redundant page_owner prefix from static symbols Ye Liu
2026-07-14 1:51 ` [PATCH v6 8/9] mm/page_owner: clamp skip_buddy_pages() PFN advance at MAX_ORDER_NR_PAGES boundary Ye Liu
2026-07-14 1:51 ` [PATCH v6 9/9] mm/page_owner: use memcg_data snapshot to avoid TOCTOU in print_page_owner_memcg() Ye Liu
2026-07-14 1:56 ` Zi Yan
2026-07-14 8:24 ` Vlastimil Babka (SUSE)
2026-07-14 3:16 ` [PATCH v6 0/9] mm/page_owner: misc cleanups Andrew Morton
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=9e9345c8-30a4-4f78-ba55-d7fa073b82d5@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=jan.kiszka@siemens.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matthew.brost@intel.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=rakie.kim@sk.com \
--cc=rostedt@goodmis.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ye.liu@linux.dev \
--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