[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210922041755.141817-1-jhubbard@nvidia.com>
Date: Tue, 21 Sep 2021 21:17:54 -0700
From: John Hubbard <jhubbard@...dia.com>
To: <o451686892@...il.com>
CC: <akpm@...ux-foundation.org>, <almasrymina@...gle.com>,
<dave.hansen@...ux.intel.com>, <jhubbard@...dia.com>,
<khandual@...ux.vnet.ibm.com>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, <mhocko@...e.com>, <minchan@...nel.org>,
<osalvador@...e.de>, <pasha.tatashin@...een.com>,
<weixugc@...gle.com>, <willy@...radead.org>,
<yang.shi@...ux.alibaba.com>, <ying.huang@...el.com>,
<ziy@...dia.com>
Subject: [PATCH 0/1] mm/migrate: de-duplicate migrate_reason strings
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@...il.com>
Cc: "Huang, Ying" <ying.huang@...el.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
Powered by blists - more mailing lists