From: Kris Van Hees <email@example.com> To: Alexei Starovoitov <firstname.lastname@example.org> Cc: Kris Van Hees <email@example.com>, Steven Rostedt <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [RFC PATCH 00/11] bpf, trace, dtrace: DTrace BPF program type implementation and sample use Date: Fri, 24 May 2019 00:05:27 -0400 Message-ID: <20190524040527.GU2422@oracle.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, May 23, 2019 at 02:13:31PM -0700, Alexei Starovoitov wrote: > On Thu, May 23, 2019 at 01:46:10AM -0400, Kris Van Hees wrote: > > > > I think there is a difference between a solution and a good solution. Adding > > a lot of knowledge in the userspace component about how things are imeplemented > > at the kernel level makes for a more fragile infrastructure and involves > > breaking down well established boundaries in DTrace that are part of the design > > specifically to ensure that userspace doesn't need to depend on such intimate > > knowledge. > > argh. see more below. This is fundamental disagreement. > > > > > Another advantage of being able to operate on a more abstract probe concept > > > > that is not tied to a specific probe type is that the userspace component does > > > > not need to know about the implementation details of the specific probes. > > > > > > If that is indeed the case that dtrace is broken _by design_ > > > and nothing on the kernel side can fix it. > > > > > > bpf prog attached to NMI is running in NMI. > > > That is very different execution context vs kprobe. > > > kprobe execution context is also different from syscall. > > > > > > The user writing the script has to be aware in what context > > > that script will be executing. > > > > The design behind DTrace definitely recognizes that different types of probes > > operate in different ways and have different data associated with them. That > > is why probes (in legacy DTrace) are managed by providers, one for each type > > of probe. The providers handle the specifics of a probe type, and provide a > > generic probe API to the processing component of DTrace: > > > > SDT probes -----> SDT provider -------+ > > | > > FBT probes -----> FBT provider -------+--> DTrace engine > > | > > syscall probes -> systrace provider --+ > > > > This means that the DTrace processing component can be implemented based on a > > generic probe concept, and the providers will take care of the specifics. In > > that sense, it is similar to so many other parts of the kernel where a generic > > API is exposed so that higher level components don't need to know implementation > > details. > > > > In DTrace, people write scripts based on UAPI-style interfaces and they don't > > have to concern themselves with e.g. knowing how to get the value of the 3rd > > argument that was passed by the firing probe. All they need to know is that > > the probe will have a 3rd argument, and that the 3rd argument to *any* probe > > can be accessed as 'arg2' (or args for typed arguments, if the provider is > > capable of providing that). Different probes have different ways of passing > > arguments, and only the provider code for each probe type needs to know how > > to retrieve the argument values. > > > > Does this help bring clarity to the reasons why an abstract (generic) probe > > concept is part of DTrace's design? > > It actually sounds worse than I thought. > If dtrace script reads some kernel field it's considered to be uapi?! ouch. > It means dtrace development philosophy is incompatible with the linux kernel. > There is no way kernel is going to bend itself to make dtrace scripts > runnable if that means that all dtrace accessible fields become uapi. No, no, that is not at all what I am saying. In DTrace, the particulars of how you get to e.g. probe arguments or current task information are not something that script writers need to concern themselves about. Similar to how BPF contexts have a public (uapi) declaration and a kernel-level context declaration taht is used to actually implement accessing the data (using the is_valid_access and convert_ctx_access functions that prog types implement). DTrace exposes an abstract probe entity to script writers where they can access probe arguments as arg0 through arg9. Nothing in the userspace needs to know how you obtain the value of those arguments. So, scripts can be written for any kind of probe, and the only information that is used to verify programs is obtained from the abstract probe description (things like its unique id, number of arguments, and possible type information for each argument). The knowledge of how to get to the value of the probe arguments is only known at the level of the kernel, so that when the implementation of the probe in the kernel is modified, the mapping from actual probe to abstract representation of the probe (in the kernel) can be modified along with it, and userspace won't even notice that anything changed. Many parts of the kernel work the same way. E.g. file system implementations change, yet the API to use the file systems remains the same. > In stark contrast to dtrace all of bpf tracing scripts (bcc scripts > and bpftrace scripts) are written for specific kernel with intimate > knowledge of kernel details. They do break all the time when kernel changes. > kprobe and tracepoints are NOT uapi. All of them can change. > tracepoints are a bit more stable than kprobes, but they are not uapi. Sure, and I understand why. And in DTrace, there is an extra layer in the design of the tracing framework that isolates implementation changes at the level of the probes from what is exposed to userspace. That way changes can be made at the kernel level without worrying about the implications for userspace. Of course one can simply not care about userspace altogether, whether there is an abstraction in place or not, but the added bonus of the abstraction is that not caring about userspace won't affect userspace much :) By the way, the point behind this design is also that it doesn't enforce the use of that abstraction. Nothing prevents people from using probes directly. But it provides a generic probe concept that isolates the probe implementation details from the tracing tool.
next prev parent reply index Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-20 23:47 Kris Van Hees 2019-05-21 17:56 ` Alexei Starovoitov 2019-05-21 18:41 ` Kris Van Hees 2019-05-21 20:55 ` Alexei Starovoitov 2019-05-21 21:36 ` Steven Rostedt 2019-05-21 21:43 ` Alexei Starovoitov 2019-05-21 21:48 ` Steven Rostedt 2019-05-22 5:23 ` Kris Van Hees 2019-05-22 20:53 ` Alexei Starovoitov 2019-05-23 5:46 ` Kris Van Hees 2019-05-23 21:13 ` Alexei Starovoitov 2019-05-23 23:02 ` Steven Rostedt 2019-05-24 0:31 ` Alexei Starovoitov 2019-05-24 1:57 ` Steven Rostedt 2019-05-24 2:08 ` Alexei Starovoitov 2019-05-24 2:40 ` Steven Rostedt 2019-05-24 5:26 ` Kris Van Hees 2019-05-24 5:10 ` Kris Van Hees 2019-05-24 4:05 ` Kris Van Hees [this message] 2019-05-24 13:28 ` Steven Rostedt 2019-05-21 21:36 ` Kris Van Hees 2019-05-21 23:26 ` Alexei Starovoitov 2019-05-22 4:12 ` Kris Van Hees 2019-05-22 20:16 ` Alexei Starovoitov 2019-05-23 5:16 ` Kris Van Hees 2019-05-23 20:28 ` Alexei Starovoitov 2019-05-30 16:15 ` Kris Van Hees 2019-05-31 15:25 ` Chris Mason 2019-06-06 20:58 ` Kris Van Hees 2019-06-18 1:25 ` Kris Van Hees 2019-06-18 1:32 ` Alexei Starovoitov 2019-06-18 1:54 ` Kris Van Hees 2019-06-18 3:01 ` Alexei Starovoitov 2019-06-18 3:19 ` Kris Van Hees 2019-05-22 14:25 ` Peter Zijlstra 2019-05-22 18:22 ` Kris Van Hees 2019-05-22 19:55 ` Alexei Starovoitov 2019-05-22 20:20 ` David Miller 2019-05-23 5:19 ` Kris Van Hees 2019-05-24 7:27 ` Peter Zijlstra 2019-05-21 20:39 ` [RFC PATCH 01/11] bpf: context casting for tail call Kris Van Hees 2019-05-21 20:39 ` [RFC PATCH 02/11] bpf: add BPF_PROG_TYPE_DTRACE Kris Van Hees 2019-05-21 20:39 ` [RFC PATCH 03/11] bpf: export proto for bpf_perf_event_output helper Kris Van Hees [not found] ` <facilities> 2019-05-21 20:39 ` [RFC PATCH 04/11] trace: initial implementation of DTrace based on kernel Kris Van Hees 2019-05-21 20:39 ` [RFC PATCH 05/11] trace: update Kconfig and Makefile to include DTrace Kris Van Hees [not found] ` <features> 2019-05-21 20:39 ` [RFC PATCH 06/11] dtrace: tiny userspace tool to exercise DTrace support Kris Van Hees 2019-05-21 20:39 ` [RFC PATCH 07/11] bpf: implement writable buffers in contexts Kris Van Hees 2019-05-21 20:39 ` [RFC PATCH 08/11] perf: add perf_output_begin_forward_in_page Kris Van Hees [not found] ` <the> [not found] ` <context> 2019-05-21 20:39 ` [RFC PATCH 09/11] bpf: mark helpers explicitly whether they may change Kris Van Hees [not found] ` <helpers> 2019-05-21 20:39 ` [RFC PATCH 10/11] bpf: add bpf_buffer_reserve and bpf_buffer_commit Kris Van Hees 2019-05-21 20:40 ` [RFC PATCH 11/11] dtrace: make use of writable buffers in BPF Kris Van Hees 2019-05-21 20:48 ` [RFC PATCH 00/11] bpf, trace, dtrace: DTrace BPF program type implementation and sample use Kris Van Hees 2019-05-21 20:54 ` Steven Rostedt 2019-05-21 20:56 ` Alexei Starovoitov
Reply instructions: You may reply publically 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=20190524040527.GU2422@oracle.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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
BPF Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/bpf/0 bpf/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 bpf bpf/ https://lore.kernel.org/bpf \ email@example.com firstname.lastname@example.org public-inbox-index bpf Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.bpf AGPL code for this site: git clone https://public-inbox.org/ public-inbox