All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	lsf-pc@lists.linux-foundation.org,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: [LSF/MM/BPF TOPIC] multi kprobe updates
Date: Thu, 22 Feb 2024 11:18:33 +0100	[thread overview]
Message-ID: <ZdcfedGHCwxOI29a@krava> (raw)

There's few ongoing kprobe multi features that I'd like to give an update
about and discuss.

- Support to execute bpf program for both entry and return probes. This
  way we don't need to create 2 links when we need to run bpf program on
  entry/return probes of the same function, first rfc posted [0].

- In addition to above feature introduce shared 'session' data between
  entry and exit probe accessible from bpf program, originally discussed
  in [1].

- Allow to use per program re-entry checks instead of current hard coded
  per cpu re-entry check, or just change to per program check directly.

- There's ongoing development of patchset moving fprobe implementation
  from function tracer on top of fgraph tracer by Masami Hiramatsu [2].
  As kprobe multi link is implemented via fprobe I'd like to give an
  update what this change means for kprobe multi link.


[0] https://lore.kernel.org/bpf/20240207153550.856536-1-jolsa@kernel.org/
[1] https://lore.kernel.org/bpf/CAEf4Bzb6sPXAtDVke=CtCXev0mxhfgEG_O-xUA-e9-8NnbBtJQ@mail.gmail.com/
[2] https://lore.kernel.org/bpf/170723204881.502590.11906735097521170661.stgit@devnote2/

             reply	other threads:[~2024-02-22 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 10:18 Jiri Olsa [this message]
2024-02-25 22:38 ` [LSF/MM/BPF TOPIC] multi kprobe updates Masami Hiramatsu

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=ZdcfedGHCwxOI29a@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.