From: Steven Rostedt <rostedt@goodmis.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Shakeel Butt <shakeel.butt@linux.dev>,
"David Hildenbrand (Arm)" <david@kernel.org>,
JP Kobryn <jp.kobryn@linux.dev>,
linux-mm@kvack.org, willy@infradead.org, usama.arif@linux.dev,
akpm@linux-foundation.org, mhocko@suse.com, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, kasong@tencent.com,
qi.zheng@linux.dev, baohua@kernel.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, chrisl@kernel.org,
shikemeng@huaweicloud.com, nphamcs@gmail.com,
baoquan.he@linux.dev, youngjun.park@lge.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm/lruvec: trace LRU add drains and drain-all requests
Date: Fri, 26 Jun 2026 06:23:06 -0400 [thread overview]
Message-ID: <20260626062306.44f6de42@fedora> (raw)
In-Reply-To: <1136baf3-3967-4202-9eaa-5fd667c235cf@kernel.org>
On Wed, 17 Jun 2026 20:18:57 +0200
"Vlastimil Babka (SUSE)" <vbabka@kernel.org> wrote:
> Yeah and I don't recall ever that a change to a mm tracepoint would ever
> break someone who'd complain and we'd have to revert it. These are niche
> enough. So I think the risk is low.
Note, we have literally thousands of trace events already, so the
chances of one being required by an application is rather low.
Especially since access still requires root access, which limits it to
administration tooling.
That said, if you know of a tool that uses trace events, then those
that it is likely to use can become an ABI. For mm trace evnets,
rasdaemon is the tool to worry about.
-- Steve
prev parent reply other threads:[~2026-06-26 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 19:52 [PATCH v3] mm/lruvec: trace LRU add drains and drain-all requests JP Kobryn
2026-06-10 21:03 ` Barry Song
2026-06-10 21:13 ` Shakeel Butt
2026-06-17 11:11 ` David Hildenbrand (Arm)
2026-06-17 15:03 ` Shakeel Butt
2026-06-17 18:18 ` Vlastimil Babka (SUSE)
2026-06-18 8:21 ` David Hildenbrand (Arm)
2026-06-18 8:30 ` Vlastimil Babka (SUSE)
2026-06-18 12:38 ` David Hildenbrand (Arm)
2026-06-22 16:38 ` JP Kobryn
2026-06-26 10:23 ` Steven Rostedt [this message]
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=20260626062306.44f6de42@fedora \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=jp.kobryn@linux.dev \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=qi.zheng@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=youngjun.park@lge.com \
--cc=yuanchu@google.com \
/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