From: menglong8.dong@gmail.com
To: andrii.nakryiko@gmail.com, alan.maguire@oracle.com
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org,
Menglong Dong <imagedong@tencent.com>
Subject: [PATCH bpf-next 0/2] libbpf: allow users to set kprobe/uprobe attach mode
Date: Fri, 3 Feb 2023 11:17:40 +0800 [thread overview]
Message-ID: <20230203031742.1730761-1-imagedong@tencent.com> (raw)
From: Menglong Dong <imagedong@tencent.com>
By default, libbpf will attach the kprobe/uprobe eBPF program in the
latest mode that supported by kernel. In this series, we add the support
to let users manually attach kprobe/uprobe in legacy or perf mode in the
1th patch.
And in the 2th patch, we add the selftests for it.
*** BLURB HERE ***
Menglong Dong (2):
libbpf: add support to set kprobe/uprobe attach mode
selftests/bpf: add test for legacy/perf kprobe/uprobe attach mode
tools/lib/bpf/libbpf.c | 30 ++++++++-
tools/lib/bpf/libbpf.h | 19 ++++++
.../selftests/bpf/prog_tests/attach_probe.c | 61 ++++++++++++++++++-
.../selftests/bpf/progs/test_attach_probe.c | 32 ++++++++++
4 files changed, 140 insertions(+), 2 deletions(-)
--
2.39.0
next reply other threads:[~2023-02-03 3:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 3:17 menglong8.dong [this message]
2023-02-03 3:17 ` [PATCH bpf-next 1/2] libbpf: add support " menglong8.dong
2023-02-06 19:58 ` Andrii Nakryiko
2023-02-07 2:23 ` Menglong Dong
2023-02-03 3:17 ` [PATCH bpf-next 2/2] selftests/bpf: add test for legacy/perf " menglong8.dong
2023-02-06 20:05 ` Andrii Nakryiko
2023-02-07 2:39 ` Menglong Dong
2023-02-07 22:50 ` Andrii Nakryiko
2023-02-08 11:49 ` Alan Maguire
2023-02-08 23:30 ` Andrii Nakryiko
2023-02-09 14:08 ` Menglong Dong
2023-02-09 17:13 ` 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=20230203031742.1730761-1-imagedong@tencent.com \
--to=menglong8.dong@gmail.com \
--cc=alan.maguire@oracle.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=imagedong@tencent.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®