From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
lkml <linux-kernel@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>
Subject: Re: [RFC bpf-next 4/4] selftests/bpf: Add attach bench test
Date: Thu, 28 Apr 2022 09:59:51 -0400 [thread overview]
Message-ID: <20220428095951.46eea612@gandalf.local.home> (raw)
In-Reply-To: <20220428095803.66c17c32@gandalf.local.home>
On Thu, 28 Apr 2022 09:58:03 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> I added the addresses it was mapping and found this:
>
> ffffffffa828f680 T __bpf_tramp_exit
cut and pasted the kallsyms not the avaliable filter functions, which had
this:
__bpf_tramp_exit (ffffffffa828f780)
-- Steve
next prev parent reply other threads:[~2022-04-28 14:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 12:52 [RFC bpf-next 0/4] bpf: Speed up symbol resolving in kprobe multi link Jiri Olsa
2022-04-07 12:52 ` [RFC bpf-next 1/4] kallsyms: Add kallsyms_lookup_names function Jiri Olsa
2022-04-08 0:57 ` Masami Hiramatsu
2022-04-13 7:27 ` Jiri Olsa
2022-04-08 23:19 ` Alexei Starovoitov
2022-04-09 20:24 ` Jiri Olsa
2022-04-12 20:46 ` Jiri Olsa
2022-04-15 0:47 ` Masami Hiramatsu
2022-04-15 22:39 ` Jiri Olsa
2022-04-11 22:15 ` Andrii Nakryiko
2022-04-12 20:28 ` Jiri Olsa
2022-04-07 12:52 ` [RFC bpf-next 2/4] fprobe: Resolve symbols with kallsyms_lookup_names Jiri Olsa
2022-04-08 0:58 ` Masami Hiramatsu
2022-04-07 12:52 ` [RFC bpf-next 3/4] bpf: Resolve symbols with kallsyms_lookup_names for kprobe multi link Jiri Olsa
2022-04-08 23:26 ` Alexei Starovoitov
2022-04-09 20:24 ` Jiri Olsa
2022-04-11 22:15 ` Andrii Nakryiko
2022-04-11 22:15 ` Andrii Nakryiko
2022-04-12 18:42 ` Jiri Olsa
2022-04-07 12:52 ` [RFC bpf-next 4/4] selftests/bpf: Add attach bench test Jiri Olsa
2022-04-11 22:15 ` Andrii Nakryiko
2022-04-12 0:49 ` Masami Hiramatsu
2022-04-12 22:51 ` Andrii Nakryiko
2022-04-16 14:21 ` Masami Hiramatsu
2022-04-18 17:33 ` Steven Rostedt
2022-04-28 13:58 ` Steven Rostedt
2022-04-28 13:59 ` Steven Rostedt [this message]
2022-04-28 18:59 ` Alexei Starovoitov
2022-04-28 20:05 ` Steven Rostedt
2022-04-28 23:32 ` Andrii Nakryiko
2022-04-28 23:53 ` Steven Rostedt
2022-04-29 0:09 ` Steven Rostedt
2022-04-29 0:31 ` Steven Rostedt
2022-04-13 16:44 ` Steven Rostedt
2022-04-13 16:45 ` Andrii Nakryiko
2022-04-13 16:59 ` Steven Rostedt
2022-04-13 19:02 ` Andrii Nakryiko
2022-04-12 15:44 ` Jiri Olsa
2022-04-12 22:59 ` Andrii Nakryiko
2022-04-08 23:29 ` [RFC bpf-next 0/4] bpf: Speed up symbol resolving in kprobe multi link Alexei Starovoitov
2022-04-09 20:24 ` Jiri Olsa
2022-04-11 22:15 ` Andrii Nakryiko
2022-04-11 22:18 ` Alexei Starovoitov
2022-04-11 22:21 ` Andrii Nakryiko
2022-04-12 15:46 ` Jiri Olsa
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=20220428095951.46eea612@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).