From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com,
kernel-team@fb.com, memxor@gmail.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v4 0/4] bpf: Implement two type cast kfuncs
Date: Mon, 21 Nov 2022 00:00:18 +0000 [thread overview]
Message-ID: <166898881841.4374.6902269174324571367.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221120195421.3112414-1-yhs@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 20 Nov 2022 11:54:21 -0800 you wrote:
> Currenty, a non-tracing bpf program typically has a single 'context' argument
> with predefined uapi struct type. Following these uapi struct, user is able
> to access other fields defined in uapi header. Inside the kernel, the
> user-seen 'context' argument is replaced with 'kernel context' (or 'kctx'
> in short) which can access more information than what uapi header provides.
> To access other info not in uapi header, people typically do two things:
> (1). extend uapi to access more fields rooted from 'context'.
> (2). use bpf_probe_read_kernl() helper to read particular field based on
> kctx.
> Using (1) needs uapi change and using (2) makes code more complex since
> direct memory access is not allowed.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/4] bpf: Add support for kfunc set with common btf_ids
https://git.kernel.org/bpf/bpf-next/c/cfe1456440c8
- [bpf-next,v4,2/4] bpf: Add a kfunc to type cast from bpf uapi ctx to kernel ctx
https://git.kernel.org/bpf/bpf-next/c/fd264ca02094
- [bpf-next,v4,3/4] bpf: Add a kfunc for generic type cast
https://git.kernel.org/bpf/bpf-next/c/a35b9af4ec2c
- [bpf-next,v4,4/4] bpf: Add type cast unit tests
https://git.kernel.org/bpf/bpf-next/c/58d84bee5846
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-21 0:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 19:54 [PATCH bpf-next v4 0/4] bpf: Implement two type cast kfuncs Yonghong Song
2022-11-20 19:54 ` [PATCH bpf-next v4 1/4] bpf: Add support for kfunc set with common btf_ids Yonghong Song
2022-11-20 19:54 ` [PATCH bpf-next v4 2/4] bpf: Add a kfunc to type cast from bpf uapi ctx to kernel ctx Yonghong Song
2022-11-20 19:54 ` [PATCH bpf-next v4 3/4] bpf: Add a kfunc for generic type cast Yonghong Song
2022-11-20 20:16 ` Alexei Starovoitov
2022-11-20 20:49 ` Kumar Kartikeya Dwivedi
2022-11-20 22:34 ` Alexei Starovoitov
2022-11-20 23:32 ` Alexei Starovoitov
2022-11-20 23:47 ` Alexei Starovoitov
2022-11-20 19:54 ` [PATCH bpf-next v4 4/4] bpf: Add type cast unit tests Yonghong Song
2022-11-21 0:00 ` patchwork-bot+netdevbpf [this message]
2022-11-21 2:10 ` [PATCH bpf-next v4 0/4] bpf: Implement two type cast kfuncs John Fastabend
2022-11-21 17:29 ` Yonghong Song
2022-11-22 1:48 ` John Fastabend
2022-11-22 4:52 ` Alexei Starovoitov
2022-11-23 3:18 ` John Fastabend
2022-11-23 20:46 ` Alexei Starovoitov
2022-11-29 16:30 ` Alan Maguire
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=166898881841.4374.6902269174324571367.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=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.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.