linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Caleb Sander Mateos <csander@purestorage.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Eric Mueller <emueller@purestorage.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
	Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>
Subject: Re: [PATCH] mm: remove unused mmap tracepoints
Date: Thu, 29 May 2025 14:43:27 -0400	[thread overview]
Message-ID: <20250529144327.1633825e@gandalf.local.home> (raw)
In-Reply-To: <20250528122411.16a551b1@gandalf.local.home>

On Wed, 28 May 2025 12:24:11 -0400
Steven Rostedt <rostedt@goodmis.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/

-- Steve


  reply	other threads:[~2025-05-29 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250411161746.1043239-1-csander@purestorage.com>
2025-04-11 17:22 ` Liam R. Howlett
     [not found] ` <3ucksa6coiwco3wpmcjtfwezqjigzm2zwvdvkt2ryvefzojtqy@4lda47c236uz>
2025-05-28 15:16   ` Caleb Sander Mateos
2025-05-28 15:23     ` Lorenzo Stoakes
2025-05-28 15:25       ` Caleb Sander Mateos
2025-05-28 15:45     ` Steven Rostedt
2025-05-28 15:48       ` Lorenzo Stoakes
2025-05-28 16:24         ` Steven Rostedt
2025-05-29 18:43           ` Steven Rostedt [this message]
2025-05-29 20:17             ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250529144327.1633825e@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=csander@purestorage.com \
    --cc=emueller@purestorage.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=pfalcato@suse.de \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox