[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250528122411.16a551b1@gandalf.local.home>
Date: Wed, 28 May 2025 12:24:11 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Caleb Sander Mateos <csander@...estorage.com>, Andrew Morton
<akpm@...ux-foundation.org>, "Liam R . Howlett" <Liam.Howlett@...cle.com>,
Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Eric Mueller <emueller@...estorage.com>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-mm@...ck.org, Vlastimil Babka <vbabka@...e.cz>, Jann Horn
<jannh@...gle.com>, Pedro Falcato <pfalcato@...e.de>
Subject: Re: [PATCH] mm: remove unused mmap tracepoints
On Wed, 28 May 2025 16:48:10 +0100
Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:
> Maybe reasonably straightforward with a clangd/ctags/etc. backend or
> something to track usage?
>
> In fact could do a quick-an'-dirty script to grep invocations and have a
> person run down the results to double-check or sth?
Yeah, I have a patch that shows how many static key instances exist and I
test that. But I probably could also add an option to the macro that
creates the trace function to also add something to a section when used,
and report when it isn't. Shouldn't be too hard.
-- Steve
Powered by blists - more mailing lists