[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DCYSABMLGCUG.3T4ZQDGWFW6KY@wolber.net>
Date: Sun, 21 Sep 2025 21:08:09 +0000
From: "Chuck Wolber" <chuck@...ber.net>
To: "Steven Rostedt" <rostedt@...dmis.org>, "Fuyu Zhao" <zhaofuyu@...o.com>
Cc: <ast@...nel.org>, <daniel@...earbox.net>, <andrii@...nel.org>,
<martin.lau@...ux.dev>, <song@...nel.org>, <yonghong.song@...ux.dev>,
<haoluo@...gle.com>, <jolsa@...nel.org>, <eddyz87@...il.com>,
<kpsingh@...nel.org>, <sdf@...ichev.me>, <mhiramat@...nel.org>,
<mathieu.desnoyers@...icios.com>, <shuah@...nel.org>, <willemb@...gle.com>,
<kerneljasonxing@...il.com>, <paul.chaignon@...il.com>,
<chen.dylane@...ux.dev>, <memxor@...il.com>,
<martin.kelly@...wdstrike.com>, <ameryhung@...il.com>,
<linux-kernel@...r.kernel.org>, <bpf@...r.kernel.org>,
<linux-trace-kernel@...r.kernel.org>, <linux-kselftest@...r.kernel.org>,
<yikai.lin@...o.com>
Subject: Re: [RFC PATCH bpf-next v1 0/3] bpf: Add BPF program type for
overriding tracepoint probes
On Thu Sep 18, 2025 at 3:29 PM UTC, Steven Rostedt wrote:
>
> 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.
Tagging on to this sentiment - the kernel's design is emergent and will always
remain so.
Speculative features have a very low probability of reflecting the required
design language. On the other hand, if someone needs a thing, the need will
drive the use of conformal design language.
..Ch:W..
Powered by blists - more mailing lists