[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250529161714.1d172189@gandalf.local.home>
Date: Thu, 29 May 2025 16:17:14 -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 Thu, 29 May 2025 14:43:27 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 28 May 2025 12:24:11 -0400
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > 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.
>
> Done: https://lore.kernel.org/all/20250529130138.544ffec4@gandalf.local.home/
>
And going through the list, I almost sent a patch that removed the two
events that this patch removes!
Luckily, when I ran "get_maintainers.pl" on the patch, I noticed you were
one of the maintainers and then I thought "Hmm, is this the events that are
removed that started all this?" And sure enough, it was!
This was going to be my change log:
Subject: [PATCH] mmap: Remove unused events vma_mas_szero and vma_store
When the __vma_adjust() was converted to use the vma iterator it removed
the functions vma_mas_store() and vma_mas_remove(). These functions called
the tracepoints trace_vma_mas_store() and trace_vma_mas_szero()
respectively. The calls to these tracepoints were removed but the trace
events that created the tracepoints were not removed. Each trace event can
take up to 5K of memory, and it is allocated regardless of if they are
called or not.
Remove the unused trace events.
Link: https://lore.kernel.org/all/20250529130138.544ffec4@gandalf.local.home/
Fixes: fbcc3104b843 ("mmap: convert __vma_adjust() to use vma iterator")
Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org>
-- Steve
Powered by blists - more mailing lists