All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Olsa <olsajiri@gmail.com>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	bpf@vger.kernel.org, Martin KaFai Lau <kafai@fb.com>,
	Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@chromium.org>,
	Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	Viktor Malik <vmalik@redhat.com>
Subject: Re: [PATCH RFC bpf-next 0/4] bpf: Add support to attach return prog in kprobe multi
Date: Fri, 16 Feb 2024 16:03:05 +0100	[thread overview]
Message-ID: <Zc95KbHKtfREu3ch@krava> (raw)
In-Reply-To: <20240215112722.2120471e@gandalf.local.home>

On Thu, Feb 15, 2024 at 11:27:22AM -0500, Steven Rostedt wrote:
> On Wed, 14 Feb 2024 21:55:03 +0100
> Jiri Olsa <olsajiri@gmail.com> wrote:
> 
> 
> > Masami,
> > we recently discussed the possibility to store data between entry/return probe,
> > IIUC your current patchset [0] allows that, but it seems to be shared across all
> > the tracers for the given function (__ftrace_return_to_handler).. is the plan to
> > make the shadow stack per tracer and function? /cc Steven
> 
> The shadow stack is per task, but it saves unique data per tracer per function.
> 
> It allows up to 16 different tracers attached to function graph tracing at
> a time, as there is a limited shadow stack size, which all the attached
> tracers use. Now you can create your own shadow stack per user (bpf
> program?) and have a single registered function graph user that will demux
> the data coming in and out of the function.

ok, I guess that's fgraph_reserve_data/fgraph_retrieve_data api

we'd like to share data between bpf programs executed from entry
and exit handlers, that should do it

thanks,
jirka

  reply	other threads:[~2024-02-16 15:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 15:35 [PATCH RFC bpf-next 0/4] bpf: Add support to attach return prog in kprobe multi Jiri Olsa
2024-02-07 15:35 ` [PATCH RFC bpf-next 1/4] fprobe: Add entry/exit callbacks types Jiri Olsa
2024-02-13 15:35   ` Masami Hiramatsu
2024-02-15  9:08     ` Jiri Olsa
2024-02-07 15:35 ` [PATCH RFC bpf-next 2/4] bpf: Add return prog to kprobe multi Jiri Olsa
2024-02-08 19:05   ` Alexei Starovoitov
2024-02-10 15:29     ` Jiri Olsa
2024-02-07 15:35 ` [PATCH RFC bpf-next 3/4] libbpf: Add return_prog_fd to kprobe multi opts Jiri Olsa
2024-02-07 15:35 ` [PATCH RFC bpf-next 4/4] selftests/bpf: Add kprobe multi return prog test Jiri Olsa
2024-02-08 19:35 ` [PATCH RFC bpf-next 0/4] bpf: Add support to attach return prog in kprobe multi Andrii Nakryiko
2024-02-10 15:31   ` Jiri Olsa
2024-02-13  4:06     ` Andrii Nakryiko
2024-02-13 12:09       ` Jiri Olsa
2024-02-13 18:20         ` Andrii Nakryiko
2024-02-13 21:09           ` Jiri Olsa
2024-02-14 20:55             ` Jiri Olsa
2024-02-15 16:27               ` Steven Rostedt
2024-02-16 15:03                 ` Jiri Olsa [this message]
2024-02-19 11:20             ` Viktor Malik
2024-02-19 12:43               ` Jiri Olsa
2024-02-23  9:32         ` Jiri Olsa
2024-02-29  0:43           ` Andrii Nakryiko
2024-02-29  1:25             ` Andrii Nakryiko

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=Zc95KbHKtfREu3ch@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sdf@google.com \
    --cc=songliubraving@fb.com \
    --cc=vmalik@redhat.com \
    --cc=yhs@fb.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 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.