From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: yhs@meta.com, daniel@iogearbox.net, alexei.starovoitov@gmail.com,
ast@kernel.org, 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,
dsahern@kernel.org, jolsa@kernel.org, x86@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, imagedong@tencent.com
Subject: Re: [PATCH bpf-next v10 0/3] bpf, x86: allow function arguments up to 12 for TRACING
Date: Thu, 13 Jul 2023 23:10:22 +0000 [thread overview]
Message-ID: <168928982219.26100.14061536595733832009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230713040738.1789742-1-imagedong@tencent.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 13 Jul 2023 12:07:35 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> For now, the BPF program of type BPF_PROG_TYPE_TRACING can only be used
> on the kernel functions whose arguments count less than or equal to 6, if
> not considering '> 8 bytes' struct argument. This is not friendly at all,
> as too many functions have arguments count more than 6. According to the
> current kernel version, below is a statistics of the function arguments
> count:
>
> [...]
Here is the summary with links:
- [bpf-next,v10,1/3] bpf, x86: save/restore regs with BPF_DW size
https://git.kernel.org/bpf/bpf-next/c/02a6dfa8ff43
- [bpf-next,v10,2/3] bpf, x86: allow function arguments up to 12 for TRACING
https://git.kernel.org/bpf/bpf-next/c/473e3150e30a
- [bpf-next,v10,3/3] selftests/bpf: add testcase for TRACING with 6+ arguments
https://git.kernel.org/bpf/bpf-next/c/5e9cf77d81f9
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-07-13 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 4:07 [PATCH bpf-next v10 0/3] bpf, x86: allow function arguments up to 12 for TRACING menglong8.dong
2023-07-13 4:07 ` [PATCH bpf-next v10 1/3] bpf, x86: save/restore regs with BPF_DW size menglong8.dong
2023-07-13 4:07 ` [PATCH bpf-next v10 2/3] bpf, x86: allow function arguments up to 12 for TRACING menglong8.dong
2023-07-13 4:07 ` [PATCH bpf-next v10 3/3] selftests/bpf: add testcase for TRACING with 6+ arguments menglong8.dong
2023-07-13 23: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=168928982219.26100.14061536595733832009.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--cc=haoluo@google.com \
--cc=imagedong@tencent.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=x86@kernel.org \
--cc=yhs@fb.com \
--cc=yhs@meta.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