[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <384b551e-28f0-ca7a-61b5-78f238de6e4d@nvidia.com>
Date: Tue, 21 Sep 2021 11:00:04 -0700
From: John Hubbard <jhubbard@...dia.com>
To: "Huang, Ying" <ying.huang@...el.com>,
Weizhao Ouyang <o451686892@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Anshuman Khandual <khandual@...ux.vnet.ibm.com>,
Michal Hocko <mhocko@...e.com>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Yang Shi <yang.shi@...ux.alibaba.com>, Zi Yan <ziy@...dia.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Minchan Kim <minchan@...nel.org>,
Mina Almasry <almasrymina@...gle.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Oscar Salvador <osalvador@...e.de>, Wei Xu <weixugc@...gle.com>
Subject: Re: [PATCH v2 2/2] mm/debug: sync up latest migrate_reason to
migrate_reason_names
On 9/21/21 07:06, Huang, Ying wrote:
...
>>> Can we add BUILD_BUG_ON() somewhere to capture at least some
>>> synchronization issue?
>>
>> Hi Huang, we discussed this in the v1 thread with you and John, seems you
>> missed it. Now we just add a comment to do the synchronization, and we can
>> figure out a more general way to use strings which in trace_events straight.
>
> Got it! And I think we can add the BUILD_BUG_ON() now and delete it
> when we have a better solution to deal with that. But if you can work
> out a better solution quickly, that's fine to ignore this.
>
I have a solution now, it's basically what I sent earlier. There appears to be
some confusion about it. I'll send it out as a patch that builds on top of
these two, hopefully in a few hours, if no problems pop up during testing.
thanks,
--
John Hubbard
NVIDIA
Powered by blists - more mailing lists