From: Kui-Feng Lee <sinquersw@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
andrii@kernel.org, kuifeng@meta.com
Subject: Re: [RFC bpf-next v4 5/6] libbpf: define __uptr.
Date: Wed, 28 Aug 2024 10:53:21 -0700 [thread overview]
Message-ID: <a2ceb85b-9878-40a5-b003-cb8943c2282b@gmail.com> (raw)
In-Reply-To: <CAEf4BzaDTaF9tQYjY1MSMjs2PwYM_K1XPyPOEPgFwHY-8+tcJg@mail.gmail.com>
Thanks for the review.
On 8/27/24 16:13, Andrii Nakryiko wrote:
> On Fri, Aug 16, 2024 at 12:12 PM Kui-Feng Lee <thinker.li@gmail.com> wrote:
>>
>> Make __uptr available to BPF programs to enable them to define uptrs.
>>
>> Signed-off-by: Kui-Feng Lee <thinker.li@gmail.com>
>> ---
>> tools/lib/bpf/bpf_helpers.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
>
>> diff --git a/tools/lib/bpf/bpf_helpers.h b/tools/lib/bpf/bpf_helpers.h
>> index 305c62817dd3..7ff9d947b976 100644
>> --- a/tools/lib/bpf/bpf_helpers.h
>> +++ b/tools/lib/bpf/bpf_helpers.h
>> @@ -185,6 +185,7 @@ enum libbpf_tristate {
>> #define __kptr_untrusted __attribute__((btf_type_tag("kptr_untrusted")))
>> #define __kptr __attribute__((btf_type_tag("kptr")))
>> #define __percpu_kptr __attribute__((btf_type_tag("percpu_kptr")))
>> +#define __uptr __attribute__((btf_type_tag("uptr")))
>>
>> #if defined (__clang__)
>> #define bpf_ksym_exists(sym) ({ \
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2024-08-28 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 19:12 [RFC bpf-next v4 0/6] Share user memory to BPF program through task storage map Kui-Feng Lee
2024-08-16 19:12 ` [RFC bpf-next v4 1/6] bpf: define BPF_UPTR a new enumerator of btf_field_type Kui-Feng Lee
2024-08-16 19:12 ` [RFC bpf-next v4 2/6] bpf: Parse and support "uptr" tag Kui-Feng Lee
2024-08-16 19:12 ` [RFC bpf-next v4 3/6] bpf: Handle BPF_UPTR in verifier Kui-Feng Lee
2024-08-16 19:12 ` [RFC bpf-next v4 4/6] bpf: pin, translate, and unpin __uptr from syscalls Kui-Feng Lee
2024-08-28 23:24 ` Alexei Starovoitov
2024-09-04 22:21 ` Martin KaFai Lau
2024-09-06 20:11 ` Martin KaFai Lau
2024-09-06 23:44 ` Alexei Starovoitov
2024-09-07 1:32 ` Martin KaFai Lau
2024-09-07 4:03 ` Martin KaFai Lau
2024-08-16 19:12 ` [RFC bpf-next v4 5/6] libbpf: define __uptr Kui-Feng Lee
2024-08-27 23:13 ` Andrii Nakryiko
2024-08-28 17:53 ` Kui-Feng Lee [this message]
2024-08-16 19:12 ` [RFC bpf-next v4 6/6] selftests/bpf: test __uptr on the value of a task storage map Kui-Feng Lee
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=a2ceb85b-9878-40a5-b003-cb8943c2282b@gmail.com \
--to=sinquersw@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=thinker.li@gmail.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