From: John Hubbard <jhubbard@nvidia.com>
To: Weizhao Ouyang <o451686892@gmail.com>,
"Huang, Ying" <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Oscar Salvador <osalvador@suse.de>,
Yang Shi <shy828301@gmail.com>, Zi Yan <ziy@nvidia.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/debug: sync up latest migrate_reason to migrate_reason_names
Date: Fri, 17 Sep 2021 17:30:16 -0700 [thread overview]
Message-ID: <3cf9bb7f-618e-4e4b-32d6-4d3c207b9a9a@nvidia.com> (raw)
In-Reply-To: <89a06743-b37a-b85a-1c04-5d863a1d2cb4@gmail.com>
On 9/17/21 02:48, Weizhao Ouyang wrote:
...
>>> const struct trace_print_flags pageflag_names[] = {
>> Good catch! Thanks!
>>
>> Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
>>
>> It may be better to use BUILD_BUG_ON() to capture similar issue earlier?
>
> How about move migrate_reason_names into mm/page_owner.c and make it size uninitialized(get rid of MR_TYPES).
> Then use BUILD_BUG_ON(ARRAY_SIZE(migrate_reason_names != MR_TYPES)) to check it?
>
A couple more thoughts:
1) From a naming and location point of view, migrate_reason_names[]
really doesn't want to be located in page_owner.c.
2) There are actually three places to synchronize, not two. And in fact,
sure enough, the MR_CONTIG_RANGE is already drifting out of synch: it
has a string of "cma" in mm/debug.c, versus "contig_range" in
include/trace/events/migrate.h.
So...is it possible to use the macro and enums in
include/trace/events/migrate.h, to define the connection between
migrate_reason and a string, everywhere?
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2021-09-18 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 6:14 Weizhao Ouyang
2021-09-17 7:03 ` Huang, Ying
2021-09-17 7:27 ` John Hubbard
2021-09-17 9:48 ` Weizhao Ouyang
2021-09-18 0:30 ` John Hubbard [this message]
2021-09-18 7:03 ` Weizhao Ouyang
2021-09-19 5:38 ` John Hubbard
2021-09-20 9:14 ` Weizhao Ouyang
2021-09-19 23:35 ` Andrew Morton
2021-09-20 9:16 ` Weizhao Ouyang
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=3cf9bb7f-618e-4e4b-32d6-4d3c207b9a9a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=o451686892@gmail.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.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