[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190521174757.74ec8937@gandalf.local.home>
Date: Tue, 21 May 2019 17:48:11 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Kris Van Hees <kris.van.hees@...cle.com>, netdev@...r.kernel.org,
bpf@...r.kernel.org, dtrace-devel@....oracle.com,
linux-kernel@...r.kernel.org, mhiramat@...nel.org, acme@...nel.org,
ast@...nel.org, daniel@...earbox.net, peterz@...radead.org
Subject: Re: [RFC PATCH 00/11] bpf, trace, dtrace: DTrace BPF program type
implementation and sample use
On Tue, 21 May 2019 14:43:26 -0700
Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:
> Steve,
> sounds like you've missed all prior threads.
I probably have missed them ;-)
> The feedback was given to Kris it was very clear:
> implement dtrace the same way as bpftrace is working with bpf.
> No changes are necessary to dtrace scripts
> and no kernel changes are necessary.
Kris, I haven't been keeping up on all the discussions. But what
exactly is the issue where Dtrace can't be done the same way as the
bpftrace is done?
-- Steve
Powered by blists - more mailing lists