[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240607212738.bf55318aebd7172fadaa11c5@linux-foundation.org>
Date: Fri, 7 Jun 2024 21:27:38 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Brennan <stephen.s.brennan@...cle.com>
Cc: linux-mm@...ck.org, Vlastimil Babka <vbabka@...e.cz>,
"Vishal Moola (Oracle)" <vishal.moola@...il.com>, Omar Sandoval
<osandov@...ndov.com>, David Hildenbrand <david@...hat.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>, Hao Ge <gehao@...inos.cn>,
linux-debuggers@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] mm: convert page type macros to enum
On Fri, 7 Jun 2024 13:29:53 -0700 Stephen Brennan <stephen.s.brennan@...cle.com> wrote:
> Changing PG_slab from a page flag to a page type in commit 46df8e73a4a3
> ("mm: free up PG_slab") in has the unintended consequence of removing
> the PG_slab constant from kernel debuginfo. The commit does add the
> value to the vmcoreinfo note, which allows debuggers to find the value
> without hardcoding it. However it's most flexible to continue
> representing the constant with an enum. To that end, convert the page
> type fields into an enum. Debuggers will now be able to detect that
> PG_slab's type has changed from enum pageflags to enum pagetype.
>
> Fixes: 46df8e73a4a3 ("mm: free up PG_slab")
Should we backport this into 6.9.x?
Powered by blists - more mailing lists