From: John Hubbard <jhubbard@nvidia.com>
To: <o451686892@gmail.com>
Cc: <akpm@linux-foundation.org>, <almasrymina@google.com>,
<dave.hansen@linux.intel.com>, <jhubbard@nvidia.com>,
<khandual@linux.vnet.ibm.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <mhocko@suse.com>, <minchan@kernel.org>,
<osalvador@suse.de>, <pasha.tatashin@soleen.com>,
<weixugc@google.com>, <willy@infradead.org>,
<yang.shi@linux.alibaba.com>, <ying.huang@intel.com>,
<ziy@nvidia.com>
Subject: [PATCH 0/1] mm/migrate: de-duplicate migrate_reason strings
Date: Tue, 21 Sep 2021 21:17:54 -0700 [thread overview]
Message-ID: <20210922041755.141817-1-jhubbard@nvidia.com> (raw)
Here is a follow-up that avoids the need for a BUILD_BUG_ON().
Pre-requisite: today's linux.git, plus Weizhao Ouyang's series v2, here:
https://lore.kernel.org/all/20210921064553.293905-1-o451686892@gmail.com/
Testing: I've done some cross-compile testing with various .config's, and
a short LTP test run. However, I have not yet attempted to verify the
actual reason strings during debugging.
I also noticed that migrate_mode is correctly passed around as an enum,
but migrate_reason is inaccurately passed around as an int. Not sure if
I'll follow up on that, as there is precious little (none, actually?)
type safety assistance from the compiler in discerning between an int
and an enum, so not much value in fixing it up.
Cc: Weizhao Ouyang <o451686892@gmail.com>
Cc: "Huang, Ying" <ying.huang@intel.com>
John Hubbard (1):
mm/migrate: de-duplicate migrate_reason strings
include/linux/migrate.h | 19 +------------------
include/linux/migrate_mode.h | 13 +++++++++++++
mm/debug.c | 20 +++++++++++---------
3 files changed, 25 insertions(+), 27 deletions(-)
--
2.33.0
next reply other threads:[~2021-09-22 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 4:17 John Hubbard [this message]
2021-09-22 4:17 ` [PATCH 1/1] " John Hubbard
2021-09-22 5:53 ` Weizhao Ouyang
2021-09-22 6:00 ` John Hubbard
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=20210922041755.141817-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=o451686892@gmail.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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