[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8111b8c6-737e-4b6f-a8d1-3710e60280e2@intel.com>
Date: Thu, 15 Jan 2026 21:08:58 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Aaron Tomlin <atomlin@...mlin.com>
Cc: "David Hildenbrand (Red Hat)" <david@...nel.org>, oleg@...hat.com,
akpm@...ux-foundation.org, gregkh@...uxfoundation.org, brauner@...nel.org,
mingo@...nel.org, neelx@...e.com, sean@...e.io,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>, Andy Lutomirski
<luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>, riel@...riel.com,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [v3 PATCH 1/1] fs/proc: Expose mm_cpumask in /proc/[pid]/status
On 1/15/26 17:53, Aaron Tomlin wrote:
> Would you be amenable to this exposure if it were guarded behind a specific
> CONFIG_DEBUG option (e.g., CONFIG_DEBUG_MM_CPUMASK_INFO)?
Not really.
ABI behind a config option is still ABI.
Powered by blists - more mailing lists