From: Steven Rostedt <rostedt@goodmis.org>
To: Fuyu Zhao <zhaofuyu@vivo.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
haoluo@google.com, jolsa@kernel.org, eddyz87@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, shuah@kernel.org,
willemb@google.com, kerneljasonxing@gmail.com,
paul.chaignon@gmail.com, chen.dylane@linux.dev, memxor@gmail.com,
martin.kelly@crowdstrike.com, ameryhung@gmail.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, yikai.lin@vivo.com
Subject: Re: [RFC PATCH bpf-next v1 0/3] bpf: Add BPF program type for overriding tracepoint probes
Date: Thu, 18 Sep 2025 11:24:25 -0400 [thread overview]
Message-ID: <20250918112425.23d4d379@gandalf.local.home> (raw)
In-Reply-To: <e8e8b5e2-35fe-43cc-ba41-c84ccba189f7@vivo.com>
On Thu, 18 Sep 2025 20:33:22 +0800
Fuyu Zhao <zhaofuyu@vivo.com> wrote:
> At the moment, I don’t have a solid real-world example to provide.
> This work is still in an exploratory stage.
We shouldn't be in the business of "if you build it, they will come".
Unless there is a concrete use case now, I would not be adding anything.
My entire workflow for what I created in the tracing system was "I have a
need, I will implement it". The "need" came first. I then wrote code to
satisfy that need. It should not be the other way around.
-- Steve
next prev parent reply other threads:[~2025-09-18 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 7:22 [RFC PATCH bpf-next v1 0/3] bpf: Add BPF program type for overriding tracepoint probes Fuyu Zhao
2025-09-17 7:22 ` [RFC PATCH bpf-next v1 1/3] bpf: Introduce BPF_PROG_TYPE_RAW_TRACEPOINT_OVERRIDE Fuyu Zhao
2025-09-17 7:22 ` [RFC PATCH bpf-next v1 2/3] libbpf: Add support for BPF_PROG_TYPE_RAW_TRACEPOINT_OVERRIDE Fuyu Zhao
2025-09-17 7:22 ` [RFC PATCH bpf-next v1 3/3] selftests/bpf: Add selftest for "raw_tp.o" Fuyu Zhao
2025-09-17 19:30 ` [RFC PATCH bpf-next v1 0/3] bpf: Add BPF program type for overriding tracepoint probes Steven Rostedt
2025-09-18 12:33 ` Fuyu Zhao
2025-09-18 15:24 ` Steven Rostedt [this message]
2025-09-19 12:54 ` Fuyu Zhao
2025-09-21 21:08 ` Chuck Wolber
2025-09-17 20:02 ` Song Liu
2025-09-18 8:05 ` Fuyu Zhao
2025-09-18 8:47 ` Jiri Olsa
2025-09-18 13:15 ` Fuyu Zhao
2025-09-18 15:32 ` Steven Rostedt
2025-09-19 13:00 ` Fuyu Zhao
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=20250918112425.23d4d379@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jolsa@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.kelly@crowdstrike.com \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=memxor@gmail.com \
--cc=mhiramat@kernel.org \
--cc=paul.chaignon@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=willemb@google.com \
--cc=yikai.lin@vivo.com \
--cc=yonghong.song@linux.dev \
--cc=zhaofuyu@vivo.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