From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 00/25] libbpf: extend [ku]probe and syscall argument tracing support
Date: Mon, 23 Jan 2023 20:10:19 +0000 [thread overview]
Message-ID: <167450461965.9309.12572725678017801706.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230120200914.3008030-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 20 Jan 2023 12:08:49 -0800 you wrote:
> This patch set fixes and extends libbpf's bpf_tracing.h support for tracing
> arguments of kprobes/uprobes, and syscall as a special case.
>
> Depending on the architecture, anywhere between 3 and 8 arguments can be
> passed to a function in registers (so relevant to kprobes and uprobes), but
> before this patch set libbpf's macros in bpf_tracing.h only supported up to
> 5 arguments, which is limiting in practice. This patch set extends
> bpf_tracing.h to support up to 8 arguments, if architecture allows. This
> includes explicit PT_REGS_PARMx() macro family, as well as BPF_KPROBE() macro.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,01/25] libbpf: add support for fetching up to 8 arguments in kprobes
https://git.kernel.org/bpf/bpf-next/c/3c59623d8294
- [v2,bpf-next,02/25] libbpf: add 6th argument support for x86-64 in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/013290329a07
- [v2,bpf-next,03/25] libbpf: fix arm and arm64 specs in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/1dac40ac8742
- [v2,bpf-next,04/25] libbpf: complete mips spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/1222445a5bf6
- [v2,bpf-next,05/25] libbpf: complete powerpc spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/2eb2be30b8da
- [v2,bpf-next,06/25] libbpf: complete sparc spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/7f60f5d85e29
- [v2,bpf-next,07/25] libbpf: complete riscv arch spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/b13ed8ca7fba
- [v2,bpf-next,08/25] libbpf: fix and complete ARC spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/0ac086567916
- [v2,bpf-next,09/25] libbpf: complete LoongArch (loongarch) spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/55ff00d5393b
- [v2,bpf-next,10/25] libbpf: add BPF_UPROBE and BPF_URETPROBE macro aliases
https://git.kernel.org/bpf/bpf-next/c/ac4afd6e6fa4
- [v2,bpf-next,11/25] selftests/bpf: validate arch-specific argument registers limits
https://git.kernel.org/bpf/bpf-next/c/bc72742bebec
- [v2,bpf-next,12/25] libbpf: improve syscall tracing support in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/8ccabeef9133
- [v2,bpf-next,13/25] libbpf: define x86-64 syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/d21fbceedd90
- [v2,bpf-next,14/25] libbpf: define i386 syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/ff00f9cbd2dd
- [v2,bpf-next,15/25] libbpf: define s390x syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/e82b96a3a99f
- [v2,bpf-next,16/25] libbpf: define arm syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/3a95c42d65d5
- [v2,bpf-next,17/25] libbpf: define arm64 syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/3488ea0584bb
- [v2,bpf-next,18/25] libbpf: define mips syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/cfd0bbe91536
- [v2,bpf-next,19/25] libbpf: define powerpc syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/c1cc01a2d1d1
- [v2,bpf-next,20/25] libbpf: define sparc syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/377c15b1a2cd
- [v2,bpf-next,21/25] libbpf: define riscv syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/a0426216a320
- [v2,bpf-next,22/25] libbpf: define arc syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/2cf802737fb9
- [v2,bpf-next,23/25] libbpf: define loongarch syscall regs spec in bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/12a299f0b5c7
- [v2,bpf-next,24/25] selftests/bpf: add 6-argument syscall tracing test
https://git.kernel.org/bpf/bpf-next/c/92dc5cdfc113
- [v2,bpf-next,25/25] libbpf: clean up now not needed __PT_PARM{1-6}_SYSCALL_REG defaults
https://git.kernel.org/bpf/bpf-next/c/a4d325ae461c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-23 20:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 20:08 [PATCH v2 bpf-next 00/25] libbpf: extend [ku]probe and syscall argument tracing support Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 01/25] libbpf: add support for fetching up to 8 arguments in kprobes Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 02/25] libbpf: add 6th argument support for x86-64 in bpf_tracing.h Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 03/25] libbpf: fix arm and arm64 specs " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 04/25] libbpf: complete mips spec " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 05/25] libbpf: complete powerpc " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 06/25] libbpf: complete sparc " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 07/25] libbpf: complete riscv arch " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 08/25] libbpf: fix and complete ARC " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 09/25] libbpf: complete LoongArch (loongarch) " Andrii Nakryiko
2023-01-20 20:08 ` [PATCH v2 bpf-next 10/25] libbpf: add BPF_UPROBE and BPF_URETPROBE macro aliases Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 11/25] selftests/bpf: validate arch-specific argument registers limits Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 12/25] libbpf: improve syscall tracing support in bpf_tracing.h Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 13/25] libbpf: define x86-64 syscall regs spec " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 14/25] libbpf: define i386 " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 15/25] libbpf: define s390x " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 16/25] libbpf: define arm " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 17/25] libbpf: define arm64 " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 18/25] libbpf: define mips " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 19/25] libbpf: define powerpc " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 20/25] libbpf: define sparc " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 21/25] libbpf: define riscv " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 22/25] libbpf: define arc " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 23/25] libbpf: define loongarch " Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 24/25] selftests/bpf: add 6-argument syscall tracing test Andrii Nakryiko
2023-01-20 20:09 ` [PATCH v2 bpf-next 25/25] libbpf: clean up now not needed __PT_PARM{1-6}_SYSCALL_REG defaults Andrii Nakryiko
2023-01-23 20:10 ` patchwork-bot+netdevbpf [this message]
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=167450461965.9309.12572725678017801706.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@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